At 5:09 PM -0500 2/7/03, [EMAIL PROTECTED] wrote:
Dan --
Who's for, C's or perl's? C's for doesn't need an opcode. Perl's
arguably might, but I think we'll be better off putting the count of
things into an I register and iterating through the list as an array.
Four words: Lazy Lists.
Well
Dan --
> Who's for, C's or perl's? C's for doesn't need an opcode. Perl's
> arguably might, but I think we'll be better off putting the count of
> things into an I register and iterating through the list as an array.
Four words: Lazy Lists.
Regards,
-- Gregor
At 1:52 AM -0800 2/5/03, David wrote:
Wow, Parrot has certainly made a lot of progress since I've last looked at it.
I see Leo's answered a bunch of this already, but since I'm digging
through my mail, I'll do it as well.
1. How do you handle variant (either string or numeric) data? Do you set
David wrote:
Leo wrote:
imcc (the assembler) generates spill code, using a PerlArray.
Ah, so that's what "spill code" means. Perhaps a definition of the term in the
document might be helpful.
$ grep spill docs/*.pod :)
leo
Leo wrote:
>> 1. How do you handle variant (either string or numeric) data? Do you set
>> up one of the string registers with a string "ssss" to keep track
>> of datatypes?
> N/Y. This would need probably a new PMC type.
OK. This is pretty common with a lot of scripting languages, so I wa
David wrote:
1. How do you handle variant (either string or numeric) data? Do you set up
one of the string registers with a string "ssss" to keep track of
datatypes?
N/Y. This would need probably a new PMC type.
2. What happens if a routine needs more than 32 variables of one data
