centralizing 'export'

[Gabriel Dos Reis]

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