From: "Tobias Schlüter" <tobias.schlueter@physik.uni-muenchen.de>
To: Janus Weil <janus@gcc.gnu.org>
Cc: Tobias Burnus <burnus@net-b.de>,
Dominique Dhumieres <dominiq@lps.ens.fr>,
fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
tkoenig <tkoenig@netcologne.de>
Subject: Re: [Patch, Fortran, OOP] PR 46313: OOP-ABI issue, ALLOCATE issue, CLASS renaming issue
Date: Sun, 07 Nov 2010 16:39:00 -0000 [thread overview]
Message-ID: <4CD6D640.7040806@physik.uni-muenchen.de> (raw)
In-Reply-To: <AANLkTinw12kR=QBiFqHqBWDYwgiZERxDGhrpEq=Y=9OV@mail.gmail.com>
On 2010-11-07 16:49, Janus Weil wrote:
> Btw, what is the reason for the macro adding *two* underscores in
> front, instead of just one?
I got curious and did some googling. Tthe C standard has this:
7.1.3 Reserved identifiers
Each header declares or defines all identifiers listed in its
associated subclause, and optionally declares or defines identifiers
listed in its associated future library directions subclause and
identifiers which are always reserved either for any use or for use as
file scope identifiers.
* All identifiers that begin with an underscore and either an
uppercase letter or another underscore are always reserved for any use.
...
So if the compiler can't use a character the user can't put into
identifiers ('.' or '$'), it reverts to something that isn't allowed to
put into identifiers: two underscores in the beginning. I think the
lesson for us is: '.' and '$' aren't portable.
Cheers,
- Tobi
next prev parent reply other threads:[~2010-11-07 16:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 23:34 Dominique Dhumieres
2010-11-06 23:56 ` Janus Weil
2010-11-07 7:55 ` Tobias Burnus
2010-11-07 12:04 ` Janus Weil
2010-11-07 12:11 ` Tobias Schlüter
2010-11-07 13:19 ` Tobias Burnus
2010-11-07 14:21 ` Janus Weil
2010-11-07 15:34 ` Tobias Schlüter
2010-11-07 15:50 ` Janus Weil
2010-11-07 16:39 ` Tobias Schlüter [this message]
2010-11-07 16:30 ` Steve Kargl
-- strict thread matches above, loose matches on Subject: below --
2010-11-06 20:11 Janus Weil
2010-11-06 21:03 ` Thomas Koenig
2010-11-06 21:23 ` Janus Weil
2010-11-07 16:52 ` Tobias Burnus
2010-11-07 18:44 ` Janus Weil
2010-11-08 13:27 ` Tobias Burnus
2010-11-09 10:41 ` Janus Weil
2018-09-17 8:59 ` Bernhard Reutner-Fischer
2018-09-17 19:22 ` Janus Weil
2018-09-17 20:25 ` Janus Weil
2018-09-19 14:50 ` Bernhard Reutner-Fischer
2018-09-20 19:36 ` Janus Weil
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=4CD6D640.7040806@physik.uni-muenchen.de \
--to=tobias.schlueter@physik.uni-muenchen.de \
--cc=burnus@net-b.de \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=janus@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).