At 06:22 PM 3/29/2001 -0500, Uri Guttman wrote:
> >>>>> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
>
> >> This will probably be harder in Perl than in C because C can afford to
> >> take more time to do global optimization passes.
>
> DS> I'm hoping to have this stage of optimization in perl. Off by
> DS> default with a normal parse-and-go run (though certainly
> DS> enableable if you want), on by default with the bytecode compiler.
>
>for long running daemon type programs, any extra optimization overhead
>at startup will be well worth it. this would be a great win if it wrings
>out a decent amount of speedup. or you could make it only doable for
>bytecode and then you run that. this shouldn't be an issue with many
>systems who want that optimization pass.
There's not much point in making it doable for bytecode but not normal perl
runs, as the same engine will be there for both. (Though I suppose the main
perl interpreter would be smaller if there wasn't an optimizer in it, but I
wouldn't bet it would take up much space) Since I'm going to tend to fire
off long-running stuff in perl, I expect it'll be there for the asking. :)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
