> What is the need for CLOS? Are we trying to build a kitchen
> sink here?
To echo Michael, CLOS != multiple dispatch.
> http://dev.perl.org/rfc/256.html
"The usefulness of multiple dispatch depends on how intelligently the
dispatcher decides which variant of a multimethod is "nearest" to a
giv
Schwern explained:
> # Following RFC 256
> sub name (Foo $self) : multi {
> return $self->{name};
> }
>
> sub name (Foo $self, STRING $name) : multi {
> $self->{name} = $name;
> return $self->{name};
> }
>
> which is q
On Wed, Aug 29, 2001 at 10:49:25PM -0700, Hong Zhang wrote:
> What is the need for CLOS? Are we trying to build a kitchen
> sink here?
Umm, I think you mean "What's the need for multiple dispatch?"
Currently, if I want to write a method that does this:
my $name = $foo->name;
$foo->name(
What is the need for CLOS? Are we trying to build a kitchen
sink here?
Hong
> -Original Message-
> From: David L. Nicol [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 29, 2001 9:43 PM
> To: [EMAIL PROTECTED]
> Subject: CLOS multiple dispatch
>
>
> http://www.jwz.org/doc/java.htm
> > I sure miss multi-dispatch.
http://dev.perl.org/rfc/256.html
Damian
http://www.jwz.org/doc/java.html includes the following gripe
about Java:
> I sure miss multi-dispatch. (The CLOS notion of doing
> method lookup based on the types of all of the arguments,
> rather than just on the type of the implicit zero'th
> argument, this).
CLOS is of course the Commo
Michael G Schwern wrote:
> The idea that a class is either 'perfect' or 'complete' has to be the
> silliest, most arrogant thing I've ever heard!
So, subsequent refinements have to use a "has-a"
instead of an "is-a" relation in re: objects of the "final" class.
Maybe the inclusion of this fe
Michael G Schwern wrote:
> If you *really* wanted to write an optimized redirector, you'd
> have the redirector eliminate itself.
>
> sub foo {
> my $method = $_[0]->{"_foo"} || $_[0]->can("_foo");
> {
> no warnings 'redefine';
> *foo = $method;
> }
> goto &$meth
This arrived as part of a mailing list that I suppose I opted into
at some point:
==
More ++, Less C
Standard template libraries, abstract classes and multiparadigm programming
are keys to
high-performance
==
"Too much C++ code is just C.
On Tue, 28 Aug 2001, Sam Tregar wrote:
> Well, there's the Perl 5 reference counting solution. In normal cases
> DESTROY is called as soon as it can be. Of course we're all anxious to
> get into the leaky GC boat with Java and C# because we've heard it's
> faster. I wonder how fast it is when
On Wed, Aug 29, 2001 at 10:50:00AM -0400, Ken Fox wrote:
> Please say the file extensions are only needed to prevent a clash of the
> source file and bytecode if they're stored in the same directory...
>
> We can say "parrot foo.whatever" and parrot will do the right thing
> regardless if foo.wha
Dan wrote:
> I like it. It's a race between those and Randal's .par and .rot (for the
> bytecode) extensions.
Please say the file extensions are only needed to prevent a clash of the
source file and bytecode if they're stored in the same directory...
We can say "parrot foo.whatever" and parrot w
Brent Dax wrote:
>On the other hand, it could stop some of the really stupid uses for
>inheritance I've seen. The dumbest one was in high school Advanced
>Placement's C++ classes--the queue and stack classes inherited from the
>array class!
Oh? How could "final classes" prevent such a travest
On Wednesday 29 August 2001 07:10 am, Randal L. Schwartz wrote:
> > "Simon" == Simon Cozens <[EMAIL PROTECTED]> writes:
>
> Simon> Actually, I'm trying to make the bytecode magic be 0x13155A1.
>
> Can you swing a cluestick in my direction? Whuh?
In decimal, 20010401, or 1 April 2001, the "bi
> "Simon" == Simon Cozens <[EMAIL PROTECTED]> writes:
Simon> Actually, I'm trying to make the bytecode magic be 0x13155A1.
Can you swing a cluestick in my direction? Whuh?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<[EMAIL PROTECTED]> http://www.stonehe
On Wed, Aug 29, 2001 at 12:25:45PM +, Stephane Payrard wrote:
> > precompiled code could have the extension .dead as in
> > the parrot code is dead, it is dead parrot code, it
> > is not running
>
> In that case, "DEADC0DE" would be an appropriate heaxadecimal magic
> header just like "
Hi Leon!
On Wed, 29 Aug 2001, Leon Brocard wrote:
> Dan Sugalski sent the following bits through the ether:
>
> > I like it
>
> The following amusing entries were posted on london.pm-list but
> I haven't seen them here, so without further ado:
>
> Greg McCarroll:
> pbc could be shortened to
Dan Sugalski sent the following bits through the ether:
> I like it
The following amusing entries were posted on london.pm-list but
I haven't seen them here, so without further ado:
Greg McCarroll:
pbc could be shortened to pb, which has two meanings
precompiled byte code and pretty boy, as
> You still need to malloc() your memory; however I realize that the
> allocator can be *really* fast here. But still, you give a lot of the
> gain back during the mark-and-sweep phase, especially if you also
> move/compact the memory.
As you said, the allocator can be really fast. Most advanced
19 matches
Mail list logo
