public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakobsybren at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/44097] New: 'export' is supposed to be no keyword in gcc, but in practice it is Date: Wed, 12 May 2010 13:40:00 -0000 [thread overview] Message-ID: <bug-44097-17996@http.gcc.gnu.org/bugzilla/> (raw) Try to define a simple function: void export() { // whatever.... } This will not compile, because 'export' is considered a keyword. After googling a bit for this keyword, I found that there has been a long debate already regarding this keyword. But everywhere I look it is claimed that the only compiler that implements this keyword, is the EDG compiler. I couldn't find any reference about this for gcc. The fact that gcc -did- implement the 'export' keyword should be made more clearly in the documentation (or the keyword could be dropped, as this is going to happen anyway for the new c++0x standard AFAIK) -- Summary: 'export' is supposed to be no keyword in gcc, but in practice it is Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jakobsybren at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44097
next reply other threads:[~2010-05-12 13:40 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-12 13:40 jakobsybren at gmail dot com [this message] 2010-05-12 13:57 ` [Bug c++/44097] " paolo dot carlini at oracle dot com 2010-05-12 14:15 ` [Bug c++/44097] [C++0x] " redi at gcc dot gnu dot org 2010-05-12 14:17 ` redi at gcc dot gnu dot org
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=bug-44097-17996@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).