If the compiler goes through all the constants at compile time to find
identical ones, why not use ".const float number = 0.0"? With pmc's,
only .Sub is supported I think. But for more complex types, the best I
can think of is being able to freeze a pmc and store it into the const
table, such
With Leo's help, I'm porting Pugs's native PIL VM to Parrot (HLL "Perl6"
under "pugs_group"), and we immediately stuck on translating the notion
of a "value object" to Parrot.
First, some backgrounds from Perl 6's class hierarchy. There are three
kinds of classes in Perl 6:
"Native" classes:
On Mon, Mar 06, 2006 at 01:08:55PM +0100, Leopold Toetsch wrote:
>* opcode vs function / method
>
>open P0, "data.txt", ">"
>print P0, "sample data\n"
>
> Using opcodes for all the IO has some disadvantages:
> a) namespace pollution: all opcodes are reserved words in
