# New Ticket Created by Allison Randal
# Please include the string: [perl #41266]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41266
Consider object instantiation as a method call on a class object, rather
than
the string: [perl #41266]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41266
Consider object instantiation as a method call on a class object, rather
than an opcode on a type ID.
$P0 = get_class HLLClass
$P1
Hi all,
Here's an experiment I worked on yesterday to make creating objects a little
easier from PIR. The MakeObject library allows you to create an object by
passing its name (or, more usefully, a Key PMC) and a set of named arguments
to the initializer.
It then calls the class's BUILDALL()
On Tuesday 10 October 2006 12:23, Leopold Toetsch wrote:
PPS: new opcode variant count is 20 now.
I can imagine that we just have these:
new P0, .Class # plain form
new P0, .Class, args
new P0, [class], args
Is args a PMC (Hash) or a list of named arguments? Creating
have with object instantiation.
PPS: new opcode variant count is 20 now.
I can imagine that we just have these:
new P0, .Class # plain form
new P0, .Class, args
new P0, [class], args
leo
Am Dienstag, 10. Oktober 2006 21:32 schrieb chromatic:
new P0, [class], args
Is args a PMC (Hash) or a list of named arguments? Creating a Hash for
every initializer is a real bummer in PIR.
As said, args ought to be everything conforming to current calling
conventions.
o = new
After thinking about this a bit, it became glaringly obvious that the
right way to instantiate an object for class Foo is to do:
new P5, .Foo
Or whatever the constant value assigned to the Foo class upon its creation
is. When a class is created, it should be assigned a number, and for most
Dan Sugalski [EMAIL PROTECTED] wrote:
After thinking about this a bit, it became glaringly obvious that the
right way to instantiate an object for class Foo is to do:
new P5, .Foo
Or whatever the constant value assigned to the Foo class upon its creation
is. When a class is created, it
On Tue, 21 Oct 2003, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
After thinking about this a bit, it became glaringly obvious that the
right way to instantiate an object for class Foo is to do:
new P5, .Foo
Or whatever the constant value assigned to the Foo class
To: [EMAIL PROTECTED] (Dan Sugalski)
cc: [EMAIL PROTECTED]
Subject:Re: Object instantiation
Dan Sugalski [EMAIL PROTECTED] wrote:
After thinking about this a bit, it became glaringly obvious that the
right way to instantiate an object for class Foo is to do:
new P5
On Oct 21, 2003, at 7:14 AM, Dan Sugalski wrote:
After thinking about this a bit, it became glaringly obvious that the
right way to instantiate an object for class Foo is to do:
new P5, .Foo
Or whatever the constant value assigned to the Foo class upon its
creation
is. When a class is
On Fri, 11 Oct 2002 14:05:30 -0700, Michael Lazzaro wrote:
Maybe postfix ! on a class name means to autoinstantiate an object of
the named class only if/when first accessed:
our FancyCache $cache; # declare, but leave undef
our FancyCache! $cache;
On Thursday, October 10, 2002, at 05:11 PM, Larry Wall wrote:
my MyClass $obj = .new;
snip
my new MyClass $obj;
Thanks for the clarification. I like those two OK, personally. If I
were chained to one of those, I wouldn't chew my leg off.
Tying it together with the other thread
On Thu, 10 Oct 2002, Michael Lazzaro wrote:
: On Thursday, October 10, 2002, at 11:23 AM, John Williams wrote:
:my $obj = MyClass(...);
:
: This seems to assume that objects have a default method if you treat
: them
: like a subroutine. Kinda tcl-ish, but I don't recall anything like
14 matches
Mail list logo
