Re: pramgas as compile-time-only

[Dan Sugalski]

On Tue, 8 Aug 2000, Bart Lateur wrote:

> On Tue, 08 Aug 2000 11:33:06 -0400, Dan Sugalski wrote:
> 
> >The problem perl will always run into is that our executable code counts as 
> >data to CPUs, and lives in the D cache, along with all the data we work on. 
> >Ripping through a few 100K strings'll kill any sort of benefits to keeping 
> >the optree small
> 
> Time for subroutine threading, isntead of op threading?

Probably, depending on your definition of subroutine threading.

> That would definitely make the "compiled" code at least twice as big.

Could, yep. (Depending, of course, on what you're talking about... :)
 
> Er, I should shut up, because I haven't got a clue how Perl is (or would
> be) implemented. I suspect it's similar to P-code.

Well, right now perl 6 compiles to vapor. :) Perl 5 is more or less
p-code.

                                        Dan