This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: centralizing 'export'
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- To: Phil Edwards <phil at jaj dot com>
- Cc: libstdc++ at gcc dot gnu dot org, ncm at cantrip dot org, gcc at gcc dot gnu dot org
- Date: 13 Jun 2002 08:55:36 +0200
- Subject: Re: centralizing 'export'
- Organization: CodeSourcery, LLC
- References: <20020612173403.A4755@disaster.basement.lan> <20020612215035.C57605@cantrip.org> <20020612175533.A5037@disaster.basement.lan>
Phil Edwards <phil@jaj.com> writes:
| On Wed, Jun 12, 2002 at 09:50:35PM +0000, Nathan Myers wrote:
| > If I recall correctly, the idea about putting the "#define export"
| > line at the point where it is was to allow export to be meaningful
| > (and applied to forward declarations) until you got into the .tcc
| > header, which is supposed to have everything declared "export" if
| > you really are "compiling separate", but not if you are just
| > #include-ing the definitions in headers as we must do today.
|
| Why not just declare the class "export" in the header,
Indeed, that is the right place to put it. I don't understand why one
would wannt to put elsewhere.
-- Gaby