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
(cross-posted from
http://pugs.blogs.com/pugs/2006/03/a_tale_of_two_p.html-- this
provides some background of the ongoing Vienna^2 hackathon's
progress on bootstrapping Pugs on Perl 5 and Parrot, simultaneously, sharing
as much code and structure as possible.)
Just some short sketches as I'm quite
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:
Author: larry
Date: Sat Mar 11 08:53:07 2006
New Revision: 8104
Modified:
doc/trunk/design/syn/S06.pod
Log:
Damian tweaks, and unresolved issue on piping something to itself.
Modified: doc/trunk/design/syn/S06.pod
==
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
Moin,
On Saturday 11 March 2006 06:22, Adam Kennedy wrote:
> Tels wrote:
> > Moin,
[snip]
> Actually, that it worked on your system was intended behaviour. The bug
> that was introduced meant that installation failed only for authors
> (that is, that had Module::Install installed on their local sy
