public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/9482: math builtins are always visible
Date: Tue, 28 Jan 2003 20:16:00 -0000	[thread overview]
Message-ID: <20030128201602.12632.qmail@sources.redhat.com> (raw)

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

From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: Andreas Jaeger <aj@suse.de>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/9482: math builtins are always visible
Date: Tue, 28 Jan 2003 21:11:15 +0100

 On Tue, Jan 28, 2003 at 05:50:20PM +0100, Andreas Jaeger wrote:
 > "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> writes:
 > > My version of the standard says in 7.1.3:
 > >    All identifiers with external linkage in any of the following subclauses
 > >    (including the future library directions) are always reserved for use as
 > >    identifiers with external linkage.
 > > This doesn't mention the header file. Note that macros are a different
 > > story. These are indeed only reserved if the appropriate header in included.
 > > If you agree on this I'll close the report.
 > 
 > I do not (yet;-) agree.
 > 
 > Footnote 154 mentions: "The list of reserved identifiers with external
 > linkage includes errno, setjmp, and va_end.".
 
 This list exactly those reserved identifiers that may either be a macro
 or an identifier with external linkage. log is definitely declared with
 external linkage in math.h.
 
 > I do not think that "log" is meant here but rather meant in the item a
 > bit further, where 7.1.3 says:
 > "Each identifier with file scope listed in any of the
 >  following subclauses (including the future library directions) is
 >  reserved for use as a macro name and as an identifier with file scope
 >  in the same name space if any of its associated headers is included."
 > 
 > So, the question boils down IMO to whether "log" has "file scope" or
 > "external linkage".
 
 Most definitely external linkage. File scope would be
 static double log (double). 
 But then I'm not a language lawyer.
 
    regards  Christian
 
 -- 
 THAT'S ALL FOLKS!


             reply	other threads:[~2003-01-28 20:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 20:16 Christian Ehrhardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-28 20:26 Andreas Jaeger
2003-01-28 20:21 aj
2003-01-28 18:06 Joseph S. Myers
2003-01-28 17:56 Joseph S. Myers
2003-01-28 16:56 Andreas Jaeger
2003-01-28 16:36 Christian Ehrhardt
2003-01-28 16:06 aj

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=20030128201602.12632.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).