On Wed, 09 Aug 2000 13:58:34 +0100, Hildo Biersma wrote:
>Yikes. Class method calls should perform inheritance, subroutine calls
>should not.
I agree with that.
>Altering the language to make the two look the same is a bad
>idea, because it breaks, fatally, as soon as the class supports more
>than one object at a time.
Then, the alternative method would be NOT to use the word "sub" any more
in order to make a method.
method param {
... # this is a method, including inheritance
}
sub param {
... # this is an ordinary function; no inheritance
}
Both could well coexist withing the same module; but they can't both be
CODE refs.
--
Bart.
- Re: How to implement both object->method and module... Bart Lateur
- Re: How to implement both object->method and m... Jonathan Scott Duff
- Re: How to implement both object->method a... Hildo Biersma
- Re: How to implement both object->meth... Graham Barr
- Re: How to implement both object->... Hildo Biersma
- Re: How to implement both object... Philip Newton
- Re: How to implement both ob... Hildo Biersma
- Re: How to implement both ob... Graham Barr
- Re: How to implement both ob... Bart Lateur
- Re: How to implement both ob... Hildo Biersma
- Re: How to implement both ob... Bart Lateur
- Re: How to implement both ob... Graham Barr
- Re: How to implement both ob... Graham Barr
- Re: How to implement both ob... Bart Lateur
- Re: How to implement both object->... John Berthels
- Re: How to implement both object... Jonathan Scott Duff
- Re: How to implement both ob... Graham Barr
- Re: How to implement both ob... Chaim Frenkel
- Re: How to implement both ob... Graham Barr
- Re: How to implement both ob... Chaim Frenkel
- Re: How to implement both ob... Graham Barr
