[Tcl-bugs] [ tcl-Bugs-2928272 ] Channel Names Incorrect in Threads

[SourceForge.net <no...@so...>]

Bugs item #2928272, was opened at 2010-01-08 14:46
Message generated for change (Comment added) made by nijtmans
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=2928272&group_id=10894

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: 25. Channel System
Group: current: 8.5.8
Status: Open
Resolution: None
Priority: 8
Private: No
Submitted By: Tim Tomkinson (tomkiti)
Assigned to: Donal K. Fellows (dkf)
Summary: Channel Names Incorrect in Threads

Initial Comment:
In wish for Windows, the output of [chan names] is incorrect in threads. The following script demonstrates this:

    package require Thread
    set tid [thread::create]
    puts [thread::send $tid {chan names}]
    puts [thread::send $tid {open ~/temp.txt w}]
    puts [thread::send $tid {chan names}]

In tclsh and wish for Unix, the correct output is:

    stderr stdout stdin
    filee5cd20
    stderr stdout stdin filee5cd20

In wish for Windows, the incorrect output is:

    <blank>
    fileecff28
    stdin

The first call returns an empty string, which is well-documented in Brent Welch's book. The second call returns "stdin" instead of the new channel. Subsequent calls to "open" will produce "stdout" and "stderr" to appear, although they don't really exist.

----------------------------------------------------------------------

>Comment By: Jan Nijtmans (nijtmans)
Date: 2010-01-08 18:05

Message:
>More fallout from 2849797 I think

I don't think so: This bug is reported against
8.5.8, and #2849797 is only in 8.6!

Therefore, I don't think that the priority
should be that high.   ;-)

----------------------------------------------------------------------

Comment By: Don Porter (dgp)
Date: 2010-01-08 16:14

Message:
More fallout from 2849797 I think.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=2928272&group_id=10894