Jerry D. Hedden proposed: > I'm considering a one line addition to the threads module > to overload the string value of a thread to return its ID: > '""' => sub \&tid
Rafael Garcia-Suarez replied: > given my experience of ""-overloading, and given that > tid() and the default stringification both return a unique > id, I don't think I like the idea of adding ""-overloading > to threads. What specifically is wrong with ""-overloading? > After all, == and != are already overloaded. 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. (BTW, I went over all the other overload options, but didn't see that any of them made sense.) > I'd prefer the suggestion of Jonathan, having an import > flag to enable the stringification behaviour. Eww. Adding a flag to turn ON behavior that should have been there in the first place is yucky. (At least to my tastes which, of course, may just be all in my mouth.) __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
