Re: [RFC] Stringify a thread

demerphq wrote:
> 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.

But that's what I'm asking.  Can you currently stringify a thread object 
and get anything (useful or otherwise)?  If that operation currently 
does nothing (or errors out), then documenting that stringifying the 
object produces the TID is perfectly acceptable.  I'm just asking if 
there is any "backwards" to be compatible with...

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748