public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dewar@gnat.com (Robert Dewar)
To: jsm28@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/3190 Re: warning: `%y' yields only last 2 digits of year
Date: Tue, 12 Mar 2002 14:46:00 -0000	[thread overview]
Message-ID: <20020312224603.6272.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/3190; it has been noted by GNATS.

From: dewar@gnat.com (Robert Dewar)
To: dewar@gnat.com, jsm28@cam.ac.uk
Cc: clock@atrey.karlin.mff.cuni.cz, gcc-gnats@gcc.gnu.org,
	gcc@gcc.gnu.org, geoffk@geoffk.org
Subject: Re: c/3190 Re: warning: `%y' yields only last 2 digits of year
Date: Tue, 12 Mar 2002 17:36:04 -0500 (EST)

 But there are lots of forms which *require* the year to be output as two
 digits, and there is nothing wrong at all with doing so. To think otherwise
 is to have taken some totally bizarre viewpoint of what Y2K was all about.
 
 It's perfectly fine for example to say 01/05/02 on a check, and requiring
 2002 is a waste of ink. I don't see any *language* style issue and that
 is all that style warnings should be about. This is about *what* you
 are programming, whereas style options should be about *how* you are
 programming. 
 
 An anology would be if the compiler watched for the string "Mrs." in output
 and printed a warning saying "inappropriate term, consider using Ms instead".


             reply	other threads:[~2002-03-12 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-12 14:46 Robert Dewar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-12 15:16 Robert Dewar
2002-03-12 14:56 Joseph S. Myers
2002-03-12 14:56 Joe Buck
2002-03-12 14:16 Joseph S. Myers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020312224603.6272.qmail@sources.redhat.com \
    --to=dewar@gnat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jsm28@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).