Tom Christiansen wrote: > > I encourage one to examine how Python does this. Particularly attractive > is the way one does not have to distinguish between tie and operator > overloading there. I'll check it out. But just to clarify: This proposal means we won't be distinguishing between tie and overloading either. Any of the methods can be defined for an object, they're called automatically by Perl in the proper context. In fact, if we made this robust enough it may well make tie unnecessary (NO I'M NOT SUGGESTING THIS YET! :-). -Nate
- RFC 159 (v1) True Polymorphic Objects Perl6 RFC Librarian
- Re: RFC 159 (v1) True Polymorphic Objects Nathan Wiger
- Re: RFC 159 (v1) True Polymorphic Objects David L. Nicol
- Re: RFC 159 (v1) True Polymorphic Objects Tom Christiansen
- Re: RFC 159 (v1) True Polymorphic Objects Jonathan Scott Duff
- Re: RFC 159 (v1) True Polymorphic Objects Nathan Wiger
- Re: RFC 159 (v1) True Polymorphic Objects Tom Christiansen
- Re: RFC 159 (v1) True Polymorphic Obj... Nathan Wiger
- Re: RFC 159 (v1) True Polymorphic Objects Piers Cawley
- Re: RFC 159 (v1) True Polymorphic Objects Nathan Wiger
- Re: RFC 159 (v1) True Polymorphic Objects Damian Conway
- Re: RFC 159 (v1) True Polymorphic Objects Tom Christiansen
- Re: RFC 159 (v1) True Polymorphic Objects Damian Conway
- Re: RFC 159 (v1) True Polymorphic Objects Tom Christiansen
- Re: RFC 159 (v1) True Polymorphic Objects Jeremy Howard
- Re: RFC 159 (v1) True Polymorphic Objects Bennett Todd
- Re: RFC 159 (v1) True Polymorphic Objects Nick Ing-Simmons