On Thu, Oct 05, 2006 at 07:28:47AM -0700, Jerry Hedden wrote: > Rafael Garcia-Suarez wrote: > > After all, == and != are already overloaded. > > Jerry D. Hedden replied: > > And how is that an argument AGAINST adding ""-overloading? > > I see it as a supporting argument. IMHO, the fact that == > > and != are overloaded for threads, but "" is not, constitutes > > a bug by omission. > > Rafael Garcia-Suarez came back with: > > but eq already works for threads equality, no ? > > Equality overloading on threads objects has been in the code > "from the beginning". I didn't add it. Yes, 'eq' works on > threads objects, so technically the overloading is > necessary. However, it's there, and my opinion is that > string overloading should be added, as well, for > completeness/consistency - not to mention convenience. >
I guess what it comes down to is that somewhere, someone has written the following line of code. die "NOT A THREAD" if $thread !~ /threads=SCALAR\(0x[0-9a-f]+\)/; Despite the fact that this style of coding is not a best practice, this sort of breakage should not occur without a serious reason for it. Steve Peters [EMAIL PROTECTED]
