Re: Idea for export Implemnation

[Jason Merrill <jason at cygnus dot com>]

>>>>> Kevin Atkinson <kevinatk@home.com> writes:

 > I am glade someone has actually thought about how to implement the
 > export keyword.  Do you think you will have something ready by egcs 1.2?

No.

 >> And then there's the question of how to handle inlines; the initial
 >> implementation probably won't inline anything in an exported template.

 > I always thought that inlines should ALWAYS go in the header files.  I
 > thought the export keyword was only for non-inline templates.  Am i
 > missing something here?

I mean, expanding arbitrary inline functions within instantiations of
exported templates, not inline exported templates.

 >> Rather, the plan is for the prelinker to extract the necessary information
 >> from the object files, run the compiler on that input, and link the
 >> resulting object file into the executable.  We could do this in either of
 >> two ways:
 >> 
 >> 1) Spit everything into one file, compile it, link it in.  Do this every
 >>    time.
 >> 2) Compile each instantiation separately.  Allow the user to specify where
 >>    to store these instantiation files.  Record dependency information so
 >>    they are only regenerated when the object files they depend on change.
 >> 
 >> Again, the initial implementation will probably go with #1 for simplicity.

 > Ok but what about libraries?  Will there be no shared template
 > instations for libraries?

Libraries will be handled exactly the same way.  I'm not sure what you're
asking.

Jason