Re: GC: what is better, reuse or avoid cloning?

2001-02-10 Thread Filipe Brandenburger
Buddha M Buck wrote: I see two ways of doing this: one is allowing a string value to be shared by two or more variables, and the other one not. Why would you want to share the string value? Why did you assign the value of $foo to $bar if you really wanted to: $bar = \$foo;

Re: GC: what is better, reuse or avoid cloning?

2001-02-10 Thread Alan Burlison
Branden wrote: Any suggestions? Yes, but none of them polite. You might do well to study the way perl5 handles these issues. Alan Burlison

Running Bytecode?

2001-02-10 Thread Vijaya Kumar C
Hai, How can we run System independent Bytecode...? I need this answer asap. Beatie said thro his module we can generate system independent Bytecode. How can i run that code ? Also How to implement a compiler? vijay

Re: Another approach to vtables

2001-02-10 Thread Paolo Molaro
On 02/07/01 Edwin Steiner wrote: [snip] I thought about it once more. Maybe I was confused by the *constant* NATIVE. Are you suggesting a kind of multiple dispatch (first operand selects the vtable, second operand selects the slot in the vtable)? So $dest = $first + $second becomes

Re: Running Bytecode?

2001-02-10 Thread Simon Cozens
On Sat, Feb 10, 2001 at 03:14:29AM -0600, Vijaya Kumar C wrote: Beatie said thro his module we can generate system independent Bytecode. How can i run that code ? perldoc ByteLoader Also How to implement a compiler? For Perl 6, or just generally? Either way, that's a hell of a question to

Re: GC: what is better, reuse or avoid cloning?

2001-02-10 Thread Dan Sugalski
At 12:51 AM 2/10/2001 -0200, Branden wrote: Back to the GC issue, I was wondering something. Okay, I snipped all of this. After reading it, I'm pretty sure it makes no sense at all. Branden, I'd recommend picking up a copy of _Garbage Collection_ and reading it. The ISBN's in the perl reading

Re: PDD 2, vtables

2001-02-10 Thread Dan Sugalski
At 08:47 AM 2/10/2001 -0200, Branden wrote: Dan Sugalski wrote: The string API should be sufficiently smart to be able to convert data from one encoding to another as it's more convenient. No, the vtable functions for the variables should know how to convert from and to perl's preferred