On Tue, 29 Aug 2000, Sam Tregar wrote:

> On Tue, 29 Aug 2000, David L. Nicol wrote:
> 
> > Well then.  It is impossible to rearchitect it to make it shared
> > text? 

> I don't believe you can simply "rearchitect it to make it shared text".

That depends on what the meaning of "it" is. :-)

If "it" is primarily XS code, then I can easily imagine building a new
perl binary with the compiled XS code linked in (kind of like the current
static linking of extensions).  If "it" is primarily perl code (like
CGI.pm) then it's harder.  But if the compiler back end works out well
enough, then CGI.o could be linked into the main executable too.  Would
that solve the shared text problem?

Just because we can leave almost everything out and dynamically link it in
later doesn't mean that the default build should be so extreme.  After
all, it's rather silly to dynamically load something you're going to load
almost every time you run.

-- 
    Andy Dougherty              [EMAIL PROTECTED]
    Dept. of Physics
    Lafayette College, Easton PA 18042

Reply via email to