From: Alexandre Oliva <aoliva@redhat.com>
To: "Allen Williams" <anw@csunv.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: WELCOME to gcc-help@gcc.gnu.org
Date: Sun, 14 Sep 2003 13:55:00 -0000 [thread overview]
Message-ID: <orhe3fa2zn.fsf@livre.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <NFBBLJGIALMDFJGMEOOHAEKICJAA.anw@csunv.com>
On Sep 13, 2003, "Allen Williams" <anw@csunv.com> wrote:
> I can't find the (relatively new) static_cast, dynamic_cast, etc. in the GCC
> manual.
The GCC manual does not document the languages it compiles. That's
something left for language standardization committees. Only GCC
extensions or limitations are documented. Since the Standard C++
new-style casts aren't either, they're not documented in the manual.
> Can anyone point me to documentation on how to use these?
You can get a copy of the ISO C++ Standard directly from the standards
bodies.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2003-09-14 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1062804110.11035.ezmlm@gcc.gnu.org>
2003-09-13 0:23 ` Error on Member Initialization Allen Williams
2003-09-13 14:28 ` Eljay Love-Jensen
2003-09-14 0:39 ` WELCOME to gcc-help@gcc.gnu.org Allen Williams
2003-09-14 0:45 ` static_cast, dynamic_cast, etc Allen Williams
2003-09-14 14:58 ` Eljay Love-Jensen
2003-09-14 13:55 ` Alexandre Oliva [this message]
[not found] <1095661597.26784.ezmlm@gcc.gnu.org>
2004-09-20 7:37 ` WELCOME to gcc-help@gcc.gnu.org zhiguo ge
2006-01-27 10:08 Vincent Barat
2006-01-27 13:43 ` Alexandre Oliva
[not found] <1184073227.29349.ezmlm@gcc.gnu.org>
2007-07-10 13:19 ` Arora Yogesh-a22623
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=orhe3fa2zn.fsf@livre.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=anw@csunv.com \
--cc=gcc-help@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).