Priorities of ToDos

2003-02-28 Thread Matthias Huerlemann
Hallo Can you tell me what the priority of coroutines is? I am developing a compiler to pasm for a language that would make use of coroutines. And I don't know enough about the parrot engine to implement this myself. I guess exceptions and/or objects have higher priority at the moment (for 0.0.10

Re: This week's Perl 6 Summary

2003-02-28 Thread Leopold Toetsch
Dan Sugalski wrote: At 8:54 AM +0100 2/28/03, Leopold Toetsch wrote: I see that limitation. But currently we have a high overhead JIT. The problem is not so much program run time, but load time. Damn. Okay, what sort of metadata would be appropriate to aid in this? If it means having the assem

Re: This week's Perl 6 Summary

2003-02-28 Thread Dan Sugalski
At 8:54 AM +0100 2/28/03, Leopold Toetsch wrote: Dan Sugalski wrote: ... And with that limitation, I'd rather have a lower-overhead JIT with a win for the shorter programs than a high-overhead one with a win for long-running programs. I see that limitation. But currently we have a high overhead

Re: List datatype

2003-02-28 Thread Dan Sugalski
At 9:34 PM -0800 2/27/03, David wrote: Is there a List datatype for Parrot? I'm looking for something along the lines of what's in Python. Specifically, it should be able to do the following operations: Not yet, though we do need one. There's not much difference between a list and an array, but th

[CVS ci] Using imcc as JIT optimizer #3

2003-02-28 Thread Leopold Toetsch
This concludes for now this experiment. It works, but to do it right, it should go in the direction Angel Faus has mentioned. Also calling conventions have to be done before, to get the data flow right. With the -Oj option a mininal CFG section is created in the packfile, which is used by parrot

Re: This week's Perl 6 Summary

2003-02-28 Thread Leopold Toetsch
Dan Sugalski wrote: ... And with that limitation, I'd rather have a lower-overhead JIT with a win for the shorter programs than a high-overhead one with a win for long-running programs. I see that limitation. But currently we have a high overhead JIT. The problem is not so much program run ti

Re: [perl #21399] [PATCH]Patch to fix compiler warnings in smallobject.c

2003-02-28 Thread Leopold Toetsch
Steve Peters (via RT) wrote: The attached patch fixes a compiler warning in smallobject.c. The #define UNITS_PER_ALLOC_GROWTH_FACTOR has a value of 1.75, but is multiplied to a size_t. This patch sets UNITS_PER_ALLOC_GROWTH_FACTOR to (size_t)2. Not good. Changing values to get rid of warnin