At 7:31 PM -0400 5/18/02, Melvin Smith wrote:
>At 07:25 PM 5/18/2002 -0400, Dan Sugalski wrote:
>>># Flag handling, or at least feature enabling, should probably be done
>>># by core code. We should provide a set_feature() function
>>>
>>>Right now we have something like this:
>>>
>>> Parrot_setflag(interpreter, PARROT_CGOTO_FLAG, NULL);
>>>
>>>I'm not sure how Parrot reacts to that if computed goto isn't available
>>>on this platform, though.
>>
>>It should pitch a warning and then ignore the computed goto choice.
>>It's not a fatal error, after all.
>
>I hold a different opinion, and that is, production release of Parrot should
>choose the cores at config time, and make the fastest (non-JIT) core
>the default, assuming it is stable.
Fair enough. When we release, there should be one JIT core, one
normal core, and one safe core, and there shouldn't be a runtime
choice as there shouldn't be a reason for a choice.
In the mean time... :)
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
