public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andrew_dowden at softdesign dot net dot nz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/30867] Can we have a new __DATE__ which is sortable, eg YYYY-MM-DD
Date: Fri, 23 May 2008 22:54:00 -0000	[thread overview]
Message-ID: <20080523225341.7615.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30867-14124@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]



------- Comment #5 from andrew_dowden at softdesign dot net dot nz  2008-05-23 22:53 -------
Strongly agree, can not change existing use/std. as relates to C89/C90 etc.

Would also suggest (as minor alternative):

  __DATEI__  date index-order, numeric, sort friendly; also US-military, etc..
    output:  yyyymmdd   eg. 20080524

  __DATEI-EN__  date index-order, non-ambiguous, English(US/GB)
    output:  yyyy-Mmm-dd   eg. 2008-May-24

  __DATEI-FR__  date index-order, non-ambiguous, Français(FR)
    output:  yyyy-Mmm-dd   eg. 2008-Mai-24

  __DATEI-DE__  date index-order, non-ambiguous, Deutsch(D)   ETC..


  __TIMEI__  time index-order, 24HR, sort friendly
    output:  hh:mm:ss   eg. 10:53:14

  __TIMEN__  time index-order, 24HR, numeric, sort friendly
    output:  hhmmss   eg. 105314


-- 

andrew_dowden at softdesign dot net dot nz changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrew_dowden at softdesign
                   |                            |dot net dot nz


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30867


      parent reply	other threads:[~2008-05-23 22:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20  2:14 [Bug preprocessor/30867] New: " alf dot lacis at aiscientific dot com
2007-02-20  5:54 ` [Bug preprocessor/30867] " pinskia at gcc dot gnu dot org
2007-04-25  0:22 ` tromey at gcc dot gnu dot org
2007-04-25 17:04 ` eweddington at cso dot atmel dot com
2007-06-12 23:33 ` alf dot lacis at aiscientific dot com
2008-05-23 22:54 ` andrew_dowden at softdesign dot net dot nz [this message]

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=20080523225341.7615.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).