Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!news.glorb.com!border3.nntp.dca.giganews.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail NNTP-Posting-Date: Thu, 23 Jun 2011 19:40:01 -0500 Return-Path: Sender: std-cpp-request@vandevoorde.com Approved: austern@google.com Message-ID: <1308849997.2080.3.camel@sara> Newsgroups: comp.std.c++ From: Magnus Fromreide Subject: Re: An hexadecimal digits group separator for long 64bit addresses Organization: A noiseless patient Spider References: < f81be81a-36de-482a-ad63-480bec9a9933@x38g2000pri.googlegroups.com> Content-Type: text/plain; charset="ISO-8859-1" X-Original-Date: Thu, 23 Jun 2011 19:26:37 +0200 X-Submission-Address: std-c++-submit@vandevoorde.com To: undisclosed-recipients:; Date: Thu, 23 Jun 2011 19:32:01 CST Lines: 35 X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-Qrt4J6H4toUgYbhk2SKHmbTFln8FbThOCZMe89IpTxf1VfWSbmgxsMBJfJRnT4SqQHbN3c8bN3lUpkF!TbyqcpI58sNvDG0IC6w/FPCjik7PxRpjFaDUM4mSSrk/u5CBzjg4zw== X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 2740 Xref: x330-a1.tempe.blueboxinc.net comp.std.c++:176 On Thu, 2011-06-16 at 12:07 -0600, Yaniv Abraham wrote: > Hello Everyone, > As 64bit word processors become more and more widespread, some of > which also see embedded applications (such as the NetLogic XLP800- > family of system processors) the current syntax in C and C++ for > hexadecimal numbers notation (and thus their notation of encoding > addresses), a long string of hexadecimal digits with the 0x prefix, > become IMHO too long making it hard to interpret and grasp quickly. > Is there a proposal to `enhance' this notation in the next C/C++ > standard to make hexadecimal numbers easier to type and understand? > C/C++ can adopt the notation that technical hardware manuals are using > for a long time of using the `_' character to separate between 4 or 8 > nibbles (4bit) sequences of digits (e.g. instead of reading > 0xFFFF58AE3BBE33AC I think it will be much easier to read > 0xFFFF58AE_3BBE33AC or even 0xFFFF_58AE_3BBE_33AC). > What do you think? Anyone? I think you are to late. This would clash with user-defined literals, wouldn't it? int operator "" _1234 (int n) { return 17; } 0x12cd_1234; /MF -- [ comp.std.c++ is moderated. To submit articles, try posting with your ] [ newsreader. If that fails, use mailto:std-cpp-submit@vandevoorde.com ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.comeaucomputing.com/csc/faq.html ]