On Wed, 30 Aug 2000, Bradley M. Kuhn wrote:
> Dan Sugalski wrote:
> > At 04:25 AM 8/30/00 -0400, Bradley M. Kuhn wrote:
> > > > 2) Having a mechanism to automagically load in chunks of executable code
> > > > only when needed would be nice
> > >
> > >I would take this one a bit further:
> > >
> >
Dan Sugalski wrote:
> At 04:25 AM 8/30/00 -0400, Bradley M. Kuhn wrote:
> > > 2) Having a mechanism to automagically load in chunks of executable code
> > > only when needed would be nice
> >
> >I would take this one a bit further:
> >
> > 2a) It should be possible, at compile-time, to detect wha
At 04:25 AM 8/30/00 -0400, Bradley M. Kuhn wrote:
>Dan Sugalski wrote:
>
> > 2) Having a mechanism to automagically load in chunks of executable code
> > only when needed would be nice
>
>I would take this one a bit further:
>
> 2a) It should be possible, at compile-time, to detect what chunks wi
Dan Sugalski <[EMAIL PROTECTED]> writes:
>What I'm
>thinking of specifically could be used to yank the functions out of the
>base perl binary (which is sort of where it started) but doesn't actually
>have to be used that way on any particular platform. (Or, rather, probably
>will, but just refer
RANDOM THOUGHT (please don't hurt me):
What about allow a 'daemon-mode'? This might be really not an option, but it
could be beneficial in a sense that there would be one core, and any other
instances would be spawned child processes?
Does that make any sense? Mind you, it's still early.
Grant M.
Dan Sugalski wrote:
> 2) Having a mechanism to automagically load in chunks of executable code
> only when needed would be nice
I would take this one a bit further:
2a) It should be possible, at compile-time, to detect what chunks will be
needed and perhaps warn the user that they have go
On 29 Aug 2000, Russ Allbery wrote:
> Dan Sugalski <[EMAIL PROTECTED]> writes:
>
> > It's not unreasonable to expect this sort of feature to possibly be used
> > for more esoteric extensions to the perl core or commonly and heavily
> > used extensions. I wouldn't, for example, want to always loa
Dan Sugalski <[EMAIL PROTECTED]> writes:
> It's not unreasonable to expect this sort of feature to possibly be used
> for more esoteric extensions to the perl core or commonly and heavily
> used extensions. I wouldn't, for example, want to always load in
> DBD::Oracle or a full complex math libra
On 29 Aug 2000, Russ Allbery wrote:
> Dan Sugalski <[EMAIL PROTECTED]> writes:
>
> > 2) Having a mechanism to automagically load in chunks of executable code
> > only when needed would be nice
>
> It's not clear to me how useful this really is from an internals speed
> standpoint on modern syst
Dan Sugalski <[EMAIL PROTECTED]> writes:
> 2) Having a mechanism to automagically load in chunks of executable code
> only when needed would be nice
It's not clear to me how useful this really is from an internals speed
standpoint on modern systems. It's no longer always true that increasing
th
Folks,
I think at this point we've beaten this one to death. The obvious
conclusions seem to be:
1) Removing all functions that do X (whatever X is) may or may not buy us
anything
2) Having a mechanism to automagically load in chunks of executable code
only when needed would be nice
3) It'd b
11 matches
Mail list logo
