On Thu, Jul 05, 2001 at 11:04:29AM -0700, Hong Zhang wrote:
> I don't think object inheritence has any significant advantage.
> Since it is not widely used and understood, we should not use it
> in Perl, period.
*cough* A little harsh.
> Its functionality can be achieved by many different ways.
> What's the problem again?
>
> I mean, really, any OO shop has it's local culture, of what the base
> classes
> are and so forth.
That pretty much sounds like the problem, in a nutshell.
And shop-level is a pretty narrow point of view. What about something that I
d/l from the net, where the cod
I'm writing a little module that implements the $() and @() stuff we've been
talking about (using a source filter), and I just want to make sure I have
it right. This is the SYNOPSIS from my docs; let me know if the behavior
I'm describing is wrong.
sub Foo { '1' }
sub Bar { 1..5
Hong Zhang wrote:
>
> Say if you want Thread can be easily inserted into LinkedList,
> you can write
>
> public Thread extends Object implements Node {
> ...
> }
>
> or
>
> public Thread extends Object, Node {
> ...
> }
>
> and don't bother to implement classic linked list node.
>
> Hong
Matt Youell wrote:
>
> > > MI thing, but now it's sounding like a constructor bubbling scheme, like
>
>
> Ah, yes. I've had to deal with that problem several times in the past. The
> terminology was new to me, however.
>
> Has there been a proposed solution?
>
> Thanks,
>
> - Matt
What's th
I don't think object inheritence has any significant advantage.
Since it is not widely used and understood, we should not use it
in Perl, period.
Its functionality can be achieved by many different ways. The
anonymous class is one of them. Personally I prefer using mixin.
The mixin is similar
Matt Youell wrote:
> The terminology was new to me, however.
I made it up.
--
John Porter
> > What I was suggesting was to consider broadening what the
> > $foo : bar style postfix sub syntax allows/assists bar to do,
> > so that bars can be used to set properties OR do other stuff.
> >
> What's the practical utility of this?
1. Simplification for perl 6 implementation. I would expec
