Re: RFC 159 (v1) True Polymorphic Objects

2000-08-30 Thread Nick Ing-Simmons
Damian Conway [EMAIL PROTECTED] writes: BTW, this is not just theoretical yearnings. I have written three modules in the past year that do not work as well as they could, simply because it is not possible to overload and ||. Damian I have one too. -- Nick Ing-Simmons [EMAIL PROTECTED]

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-28 Thread Tom Christiansen
Summary: I think these should all simply break down into a single Boolification test of some sort, as occurs already with operator overload. LOGHIGHAND Called in context LOGHIGHOR Called in || context LOGLOWAND Called in and context LOGLOWOR Called in or context LOGIFELSE

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-28 Thread Damian Conway
Summary: I think these should all simply break down into a single Boolification test of some sort, as occurs already with operator overload. Counter-summary: Although the high and low precedence binary ops could be rolled together, the current version of operator

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-28 Thread Jeremy Howard
Removed perl6-announce x-post Tom Christiansen wrote: Hm I don't recall C++ ever thinking to overload the control-flow operators ("", "||", "," (that is, comma), and "?:"). Why not? Even if their "a b" should produce a more mundane 1 or 0, one still might wish control. '', '||', et

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-28 Thread Tom Christiansen
I can currently overload + * to do this, but not . That's broken. Hm I don't recall C++ ever thinking to overload the control-flow operators ("", "||", "," (that is, comma), and "?:"). Why not? Even if their "a b" should produce a more mundane 1 or 0, one still might wish control.

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-27 Thread Damian Conway
Data Conversion and Access - STRING Called in a string context NUMBER Called in a numeric context BOOLEAN Called in a boolean context Operator Overloading

RFC 159 (v1) True Polymorphic Objects

2000-08-25 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE True Polymorphic Objects =head1 VERSION Maintainer: Nathan Wiger [EMAIL PROTECTED] Date: 25 Aug 2000 Mailing List: [EMAIL PROTECTED] Version: 1 Number: 159 Status: Developing =head1

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-25 Thread Nathan Wiger
Oh geez! I'm sorry, I forgot to mention David Nicol in the REFERENCES, who also gave great input, especially on the BOOLEAN accessor. Thanks David! I swear I'll put you in v2. :-{ -Nate Perl6 RFC Librarian wrote: This and other RFCs are available on the web at http://dev.perl.org/rfc/

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-25 Thread Jonathan Scott Duff
On Fri, Aug 25, 2000 at 03:23:25PM -, Perl6 RFC Librarian wrote: Operator Overloading - PLUS Called in + context MINUSCalled in - context TIMESCalled in * context DIVIDED

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-25 Thread Nathan Wiger
Jonathan Scott Duff wrote: Operator Overloading - PLUS Called in + context MINUSCalled in - context TIMESCalled in * context DIVIDED Called in / context MODULUS

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-25 Thread Tom Christiansen
Jonathan Scott Duff wrote: Operator Overloading - PLUS Called in + context MINUSCalled in - context TIMESCalled in * context DIVIDED Called in / context MODULUS

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-25 Thread David L. Nicol
Nathan Wiger wrote: Oh geez! I'm sorry, I forgot to mention David Nicol in the REFERENCES, who also gave great input, especially on the BOOLEAN accessor. Thanks David! I swear I'll put you in v2. :-{ -Nate Whatever. You could overload FILE STRING to be a print operator

Re: RFC 159 (v1) True Polymorphic Objects

2000-08-25 Thread Tom Christiansen
You could overload FILE STRING to be a print operator returning a FILE so we can do C++ like cout "hello Bjarne" eol; That would be--and always has been--pretty darned horrible. You've managed to hide the verb completely. It's much clearer when it command verb is in the