At 02:53 AM 9/8/2001 -0400, Matthew Brooks wrote:
> From what I can tell (correct me if I'm wrong... PLEASE!) Larry is actually
>considering (or should I say, has already decided) to change $obj->method()
>to $obj.method() in Perl6.
Yup. The method call operator's changing. What the string concat operator
is going to be is still undecided last I knew.
>Also, I think I recall there being mention of being able to precompile your
>code using Perl itself (no need for Perl2exe or ActiveState's PerlApp) in
>Perl6, is that true?
Yep, that's one of the plans. How well this works and, more to the point,
how small the resulting executable will be is going to depend a lot on the
code being compiled. Having string eval, require, or do means you need the
whole compiler suite handy. (You also need to link in any binary
extensions, so things could get large)
There will definitely be a compile-to-bytecode mode, at least, which'll
just need the parrot bytecode engine to execute. (Assuming, of course, no
string eval, require, or do, in which case you'll need the whole compiler
suite again) It isn't that big a leap to go from bytecode to C or direct
machine language once you have a bytecode engine, so I expect we'll
leverage it to do what we need.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
