From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Fri, 24 Mar 2006 19:29:47 +0100
On Mar 24, 2006, at 18:38, Chip Salzenberg wrote:
> On Fri, Mar 24, 2006 at 04:23:53PM +0100, Leopold Toetsch wrote:
> . . .
>> cl = getclass 'MyClass'
>> o = __instantiate(cl, p0, p1, 'extra
Leopold Toetsch wrote:
> ...Folks are creating custom object.build
> methods, which after __init was called, initialize the object more.
Yes, I'm doing this at the moment. It's workable but has the overhead of
an extra method call.
> ... Above scheme (a function call with
> standardized name) a
On Mar 24, 2006, at 18:38, Chip Salzenberg wrote:
On Fri, Mar 24, 2006 at 04:23:53PM +0100, Leopold Toetsch wrote:
There are currently 14 opcode variants of C, not counting
C. But all are limited when it comes to initializers.
What's the situation in which instantiate is required because the
Multimethod constructors? That's one thing that, as far as I know, is
missing from parrot and could be resolved with this. Although the
potential to create an array for sprintf with one opcode does sound
nice, or at least one line of pir.
On Mar 24, 2006, at 11:38 AM, Chip Salzenberg wrote:
On Fri, Mar 24, 2006 at 04:23:53PM +0100, Leopold Toetsch wrote:
> There are currently 14 opcode variants of C, not counting
> C. But all are limited when it comes to initializers.
What's the situation in which instantiate is required because the current
arrangment doesn't work? Generally, it's
There are currently 14 opcode variants of C, not counting
C. But all are limited when it comes to initializers.
I've now experimented (again) with C [1], which got
deactivate during calling conv changes.
Here is a typical sequence with new:
o = new .Integer
o = 42
and the same with inst
