From: gcc@integrable-solutions.net
To: gcc@gcc.gnu.org
Cc: jason@redhat.com
Subject: C++: Anticipated declaration of builtins
Date: Sun, 25 May 2003 22:13:00 -0000 [thread overview]
Message-ID: <m2vfvy4ur5.fsf@dromion.integrable-solutions.net> (raw)
Hi,
Currently, anticipated declarations of builtin functions whose names do
not begin with underscores are done as follows:
* a pre-declaration at the standard namespace scope std::
* a pre-declaration at the global scope.
The actual code reads:
/* All builtins that don't begin with an '_' should additionally
go in the 'std' namespace. */
if (name[0] != '_')
{
push_namespace (std_identifier);
builtin_function_1 (name, type, std_node, code, class, libname, attrs);
pop_namespace ();
}
return builtin_function_1 (name, type, NULL_TREE, code,
class, libname, attrs);
I have two questions:
1) Shouldn't we pre-declare the function at global scope, then do a
using-declaration at the standard scope?
2) Why doesn't the second call to builtin_function_1() specify
global_namespace instead of NULL_TREE? I think specifying
global_namespace should be the way to go. What I am missing?
Thanks,
-- Gaby
next reply other threads:[~2003-05-25 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-25 22:13 gcc [this message]
2003-05-26 0:33 Roger Sayle
2003-05-26 2:08 ` Gabriel Dos Reis
2003-05-26 2:44 ` Roger Sayle
2003-05-26 4:26 ` Gabriel Dos Reis
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=m2vfvy4ur5.fsf@dromion.integrable-solutions.net \
--to=gcc@integrable-solutions.net \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
/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).