Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 11:27 AM +0200 9/3/04, Leopold Toetsch wrote:
>>Dan Sugalski <[EMAIL PROTECTED]> wrote:
>>> At 12:16 PM +0200 8/31/04, Leopold Toetsch wrote:
Pclass = getclass, "Foo"
Pobjnew = Pclass."__new"(args) # Pnew is an OUT argument
At 11:27 AM +0200 9/3/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
At 12:16 PM +0200 8/31/04, Leopold Toetsch wrote:
Pclass = getclass, "Foo"
Pobjnew = Pclass."__new"(args) # Pnew is an OUT argument
and that be special-cased to call VTABLE_new according to calling
co
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 12:16 PM +0200 8/31/04, Leopold Toetsch wrote:
>>
>>Pclass = getclass, "Foo"
>>Pobjnew = Pclass."__new"(args) # Pnew is an OUT argument
>>
>>and that be special-cased to call VTABLE_new according to calling
>>conventions.
> Still don't like __n
At 12:16 PM +0200 8/31/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
Add a vtable slot to the PMC vtable inv_init (or something like that,
the name's not that big a deal),
vtable->new and "__new"?
Those are a little too similarly named. We should have something more
distin
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Add a vtable slot to the PMC vtable inv_init (or something like that,
> the name's not that big a deal),
vtable->new and "__new"?
> ... define it as an invokable method
> taking parameters as the current calling conventions, and be done
> with it. Basi
