On 10/4/06, John Peacock <[EMAIL PROTECTED]> wrote:
Jerry Hedden wrote:
> Does it have to be? For example, according to CPANTS there are no CPAN
> modules that have 'threads' as a requirement other than
> 'thread::shared', 'Thread::Suspend' and 'Thread::Cancel', and I know
> they won't break.
The world isn't CPAN; there may be lots of private code which uses
'threads' which you won't ever find out about.
More to the point, however, is what does it do _now_, i.e. can you
currently stringify a thread object at all? If that concept isn't
available now, this has nothing do to with 'backwards compatibility' at
all, since you are introducing new behavior...
Thats the problem with having default stringification behaviour.
Unless you explicitly document the stringification behaviour as being
open to change people are allowed to assume it wont and use the
default behaviour.
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
