Prev: very important web site to post you know your political protests....
Next: FAQ 3.13 How can I use curses with Perl?
From: Ilya Zakharevich on 9 Feb 2010 23:17 On 2010-02-09, Ben Morrow <ben(a)morrow.me.uk> wrote: >> > Would you agree with me that new overload types >> > *must* default to falling back >> How would "new" types be different from the "old" ones? The problem >> existed back then; what changed? > What changed is that there are now published classes that use some > overloading, don't specify fallback, and don't overload the new type. > Take for example the new "qr" overload. Under 5.10 and earlier, treating > an object as a regex would invoke the stringify overload, so 5.12 must > continue to do so for objects that don't have a qr overload *even* if > fallback was not requested. Hmm, I deduce that under "overload types" you meant "overloaded operation"? If, yes, of course... Ilya
From: Ben Morrow on 10 Feb 2010 07:18
Quoth Ilya Zakharevich <nospam-abuse(a)ilyaz.org>: > On 2010-02-09, Ben Morrow <ben(a)morrow.me.uk> wrote: > >> > Would you agree with me that new overload types > >> > *must* default to falling back > > >> How would "new" types be different from the "old" ones? The problem > >> existed back then; what changed? > > > What changed is that there are now published classes that use some > > overloading, don't specify fallback, and don't overload the new type. > > Take for example the new "qr" overload. Under 5.10 and earlier, treating > > an object as a regex would invoke the stringify overload, so 5.12 must > > continue to do so for objects that don't have a qr overload *even* if > > fallback was not requested. > > Hmm, I deduce that under "overload types" you meant "overloaded > operation"? If, yes, of course... Yes, sorry, it was a poor choice of word. 'Type of overload' rather than 'type' as in 'class'. Ben |