Why not a Perl that can be compiled as an executable OR a daemon with run-time loading of modules like Apache? or even dynamic modules (*.so, *.dll). This would allow an admin to simply change the .conf file to load the needed modules and libraries and restart the daemon... or perhaps a compiled-in AutoLoader. This way Perl could have pre-compiled libraries (like C) and a minimalistic core, while still retaining all of the functionality of full implementation of Perl. If you used an AutoLoader feature you could permit site-specific libraries to remain in memory while others are dynamically loaded and released when needed. The plus behind this sort of environment would be that any updates would be able to be library or core specific, and that backward compatibility could be maintained by simply loading the appropriate module for that particular script (i.e., 'use Perl6;'). Grant M. ----- Original Message ----- From: "Steve Simmons" <firstname.lastname@example.org> To: <email@example.com> Sent: Sunday, July 30, 2000 10:56 PM Subject: Re: Working Group Proposal > Implicit in the second paragraph is that any perl which is built > with some features compiled out of the core should automaticly have > those features moved into the modules. > > IMHO (and I speak from experience here) it would be a big win to be > able to, at build time, compile any well-behaved module into the > perl core. We have a number of modules which we effectively require > be in every perl application (carp, strict, Dumper, more); it'd be > nice if the `standard' corporate perl executable simply had them > all in it rather than load them on each of the thousands and thousands > of perl runs we do daily.