centralizing 'export'

[Phil Edwards]

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, and not touch any
of the out-of-class definitions?  Supposed to have the same effect, right?


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams