Anyone think that having Thread contain - and specifically the point print()
and toString() methods represent - a thread "name"?
I'm not sure how this would be exactly, but it would be a nice debugging
helper. Naturally one would still be able to create one without a name.

Sounds like an excellent idea. Too bad it won't show up in the debugger
because the OS won't know about the thread name.
Sean
"Matthew Wilson" <dmd synesis.com.au> wrote in message
news:b808h7$20nh$1 digitaldaemon.com...

Anyone think that having Thread contain - and specifically the point

and toString() methods represent - a thread "name"?
I'm not sure how this would be exactly, but it would be a nice debugging
helper. Naturally one would still be able to create one without a name.

Perhaps we could initialize a table with the thread ids and names, and the
debugger could inspect it somehow.
"Sean L. Palmer" <palmer.sean verizon.net> escreveu na mensagem
news:b818sc$2lsc$1 digitaldaemon.com...

Sounds like an excellent idea. Too bad it won't show up in the debugger
because the OS won't know about the thread name.
Sean
"Matthew Wilson" <dmd synesis.com.au> wrote in message
news:b808h7$20nh$1 digitaldaemon.com...

Anyone think that having Thread contain - and specifically the point

and toString() methods represent - a thread "name"?
I'm not sure how this would be exactly, but it would be a nice debugging
helper. Naturally one would still be able to create one without a name.