[Bug c++/44097] New: 'export' is supposed to be no keyword in gcc, but in practice it is

[Bug c++/44097] New: 'export' is supposed to be no keyword in gcc, but in practice it is

[jakobsybren at gmail dot com]

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

[Bug c++/44097] 'export' is supposed to be no keyword in gcc, but in practice it is

[paolo dot carlini at oracle dot com]

------- Comment #1 from paolo dot carlini at oracle dot com  2010-05-12 13:57 -------
Well, one thing is *reserving* a keyword, another implementing a semantics.
About the next Standard, yes it could make sense to drop it from the set of
keywords, but I don't think we should rush to do that, certainly not in the
obsolete, and not maintained anymore, 4.1.x branch ;)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44097

[Bug c++/44097] [C++0x] 'export' is supposed to be no keyword in gcc, but in practice it is

[redi at gcc dot gnu dot org]

------- Comment #2 from redi at gcc dot gnu dot org  2010-05-12 14:15 -------
export is still going to be a keyword in C++1x, even though the feature has
been removed, so it should still be recognised as a keyword by GCC.


-- 

redi at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44097

[Bug c++/44097] [C++0x] 'export' is supposed to be no keyword in gcc, but in practice it is

[redi at gcc dot gnu dot org]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]



------- Comment #3 from redi at gcc dot gnu dot org  2010-05-12 14:16 -------
2.12 Keywords [lex.key]
1 The identifiers shown in Table 3 are reserved for use as keywords (that
is, they are unconditionally treated as keywords in phase 7) except in an
attribute-token (7.6.1) [ Note: The export keyword is unused but is
reserved for future use. — end note ]:


N.B. "unconditionally treated as keywords"


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44097