On Sun, 06 Aug 2000 17:20:06 -0700, Nathan Wiger wrote: >I'm not against other names. You're right, STRINGIFY has a ring to it, >but I worry it might be too catchy for its own good? Not sure. > >The reason I thought SCALAR was good was because of this: > > print scalar $object; > >If this calls $object->SCALAR (I think it would) then I think that's a >compelling argument on its own. It sounds to me like an object would no longer be a scalar. Heh?!? STRINGIFY would have my vote. "It's a string!!!". A string is a very specific subtype of scalar. -- Bart.
- RFC 49 (v1) Objects should have builtin string SCALA Perl6 RFC Librarian
- Re: RFC 49 (v1) Objects should have builtin strin... Peter Scott
- Re: RFC 49 (v1) Objects should have builtin s... Spider Boardman
- Re: RFC 49 (v1) Objects should have built... Nathan Wiger
- Re: RFC 49 (v1) Objects should have b... Bart Lateur
- Re: RFC 49 (v1) Objects should h... Peter Scott
- Re: RFC 49 (v1) Objects should have built... Damian Conway
- Re: RFC 49 (v1) Objects should have b... Nathan Wiger
- Overloading && || Nick Ing-Simmons
- Re: Overloading && || Peter Scott
- Re: Overloading && |... Nick Ing-Simmons
- Re: Overloading &&am... Peter Scott
- Re: Overloading && || Damian Conway
- Re: Overloading && || Damian Conway
- Re: Overloading && || Peter Scott