On Tue, Aug 3, 2010 at 6:11 AM, Jonathan Worthington wrote:
> On 02/08/2010 08:05, Peter Lobsinger wrote:
>>
>> On Fri, Jul 30, 2010 at 8:08 PM, Jonathan Worthington
>> wrote:
>>
>>>
>>> Here's one critical thing, however. This is _not_ about a constant
>>> segment.
>>> I could have a module...
On 02/08/2010 08:05, Peter Lobsinger wrote:
On Fri, Jul 30, 2010 at 8:08 PM, Jonathan Worthington
wrote:
Here's one critical thing, however. This is _not_ about a constant segment.
I could have a module...
class Lolspeak {
method lol() { say "oh lol" }
}
That I pre-compile to a PBC. I
On Fri, Jul 30, 2010 at 8:08 PM, Jonathan Worthington
wrote:
> chromatic wrote:
>>
>> Rakudo and other HLLs could greatly benefit from Parrot sorting out the
>> "How and when do I declare a class?" mess. The best way I can see for us to
>> help them is to ease the requirement that all classes nee
chromatic wrote:
Rakudo and other HLLs could greatly benefit from Parrot sorting out the "How
and when do I declare a class?" mess. The best way I can see for us to help
them is to ease the requirement that all classes need declaration in :load
:init subs when compiling PIR or loading PBC by a
On Wed, Jul 28, 2010 at 08:42:44PM -0700, Peter Lobsinger wrote:
> AFAIK, classes freeze and thaw fine.
>
> .sub 'FooClass' :anon :immediate
> $P0 = newclass 'Foo'
> .return ($P0)
> .end
>
> .sub 'main' :main
> # .const 'Sub' $P0 = 'FooClass'
> $P0 = get_class 'Foo'
> $S0 = $P
On Wednesday 28 July 2010 at 20:42, Peter Lobsinger wrote:
> I am not sure we need another segment for this. Classes are just
> objects. If freeze-thaw isn't cutting it for classes, I think it is
> more indicative of general freeze-thaw issues than a situation that
> requires special-casing classe
On Wed, Jul 28, 2010 at 6:02 PM, chromatic wrote:
> Rakudo and other HLLs could greatly benefit from Parrot sorting out the "How
> and when do I declare a class?" mess. The best way I can see for us to help
> them is to ease the requirement that all classes need declaration in :load
> :init subs
Rakudo and other HLLs could greatly benefit from Parrot sorting out the "How
and when do I declare a class?" mess. The best way I can see for us to help
them is to ease the requirement that all classes need declaration in :load
:init subs when compiling PIR or loading PBC by adding a bytecode s
