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 ABS
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/
>
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
> Everything in Perl becomes an object, using existing object-syntax. Out of
> plain sight, there would be essentially three base classes: Scalar, List,
> and Hash.
Arg! You beat me to it. :-) This was the next RFC on my list.
> Stricter typing would be imposed (as needed) at the object level
>
Jonathan Scott Duff wrote:
>
> >Operator Overloading
> >-
> >PLUS Called in + context
> >MINUSCalled in - context
> >TIMESCalled in * context
> >DIVIDED Called in / context
> >
>Jonathan Scott Duff wrote:
>>
>> >Operator Overloading
>> >-
>> >PLUS Called in + context
>> >MINUSCalled in - context
>> >TIMESCalled in * context
>> >DIVIDED Called in / context
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 a
>That's their problem. Perl is extremely useful to Unix systems
>programmers and administrators. They are the target audience
>that Perl was initially written for, whom it was made famous by,
>and you will find that it continues to be very important to us.
>If you relegate us to take a back sea
>Come on Tom take it easy on us poor admins who have to live in the "Billduh"
>world.
So long as such folks do nothing that will hurt those of us who
have no trek with such, then live and let live. But when Billness
starts biting those who won't have anything to do with it causing strange
acti
Amen.
-Original Message-
From: Tom Christiansen [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 25, 2000 3:09 PM
To: Lipscomb, Al
Cc: Joe McMahon; Stephen P. Potter; Michael Maraist;
[EMAIL PROTECTED]; 'Larry Wall'
Subject: Re: RFC 146 (v1) Remove socket functions from core
>Come on To
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 operato
>You could overload
> FILE < STRING
>to be a print operator returning a FILE so we can do C++ like
> cout << "hello Bjarne" <
Please discuss this RFC on the -objects sublist. Thanks.
Matt, you should probably update the Mailist List to
perl6-language-objects for v2.
-Nate
Perl6 RFC Librarian wrote:
>
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> OO Integration/M
13 matches
Mail list logo
