Clayton Scott wrote: > I first thought that "==" and "eq" were cut from the same cloth as > "||" and "or" that is the difference was precedence. Then I learned. Mr. Scott's experience is evidence for a strong argument AGAINST operator overloading. If we allow object types, and allow object types to overload, we lose the clarity we have in a language that doesn't have these things. Maintaining code with perl5 package-modules is difficult enough, but at least all the object method calls are explicitly object method calls and there aren't any object method calls masquerading as well-understood builtins! -- David Nicol 816.235.1187 [EMAIL PROTECTED] On hold for tech support since 1995
- Re: RFC 54 (v1) Operators: Polymorphic comparisons Jean-Louis Leroy
- Re: RFC 54 (v1) Operators: Polymorphic comparisons Chaim Frenkel
- Re: RFC 54 (v1) Operators: Polymorphic comparisons Peter Scott
- Re: RFC 54 (v1) Operators: Polymorphic comparisons Damian Conway
- Re: RFC 54 (v1) Operators: Polymorphic comparisons Damian Conway
- Re: RFC 54 (v1) Operators: Polymorphic comparisons Glenn Linderman
- Re: RFC 54 (v1) Operators: Polymorphic comparisons Chaim Frenkel
- Re: RFC 54 (v1) Operators: Polymorphic compariso... Dan Sugalski
- Re: RFC 54 (v1) Operators: Polymorphic compa... Clayton Scott
- Re: RFC 54 (v1) Operators: Polymorphic c... David L. Nicol
- Re: RFC 54 (v1) Operators: Polymorphic c... Damian Conway
- Re: RFC 54 (v1) Operators: Polymorphic comparisons Hildo Biersma
- Re: RFC 54 (v1) Operators: Polymorphic comparisons Michael Fowler