Re: [tcljava-dev] Channel mapping for stdin, stdout, etc.

[Christian K. <chr...@so...>]

Hello,

David L. Smith-Uchida wrote:

> Hmmm....Looking back through the mailing list archive there was a bug
> 221678 which asserts that the channels for standard in, out and err should
> have dual names stdin/file0 stdout/file1 stderr/file2.  It seems as though
> there's a problem with channels having dual names and error reporting.

Jup, that was exactly the problem: You have two names for the standard channels
(e.g. file0 and stdin for standard input), and Jacl always used the fileX name
in error messages, whereas Tcl uses exactly the name the user specified.
So the bug was simply that Jacl behaved differently from Tcl.

> Also, is there a requirement that stdin == file0, etc?  Is this an alias?

No such requirement is specified in any man page or test file of Tcl.
But as a long term user of Tcl (starting with version ~7.0) you are used to
get the answer "file3" when opening your first file interactivly, like this:
  # tclsh8.3
  % open /etc/passwd
  file3
And Jacl used to return file0...

Both effects (defects?) are unrelated to your problem with the hardwired
channel mapping of e.g. stdin to System.in.

Greetings, Krischan
-- 
Christian Krone, SQL Datenbanksysteme GmbH
Mail mailto:chr...@so...