Properties and stricture
Afaict, even with use strict at its most strict, perl 6 can't (in practice) complain, at compile time, if $foo.Foun refers to an undeclared Foun. Right? Should there be a strict mode that warns if a method name matches a built in property name?
RE: Python...
> Perl is far more practical than experimental. Not at the moment. That's the problem. (Note the subtle subject change back to its original intent.) p
Re: Stacks, registers, and bytecode. (Oh, my!)
Hong Zhang wrote: > > based scheme itself. For example, an local variable is not used by > any of the code, however an eval($s) may refer to it. So should optimizer > eliminate the local? > > Hong mark blocks that have closures in them, in those, you can't throw any locals out. Otherwise, you can throw them out if youre not going to use them -- David Nicol 816.235.1187 [EMAIL PROTECTED] "Obi-Wan taught me mysticism" -- Luke Housego
