This page is intended as a discussion platform with the goal to possibly obtain a console behaviour improvement to being proposed as a TIP.
Refer also to LV's question here: console
In both cases discussed below, it must be differentiated between invokes from a native OS's console and invokes from e.g. a desktop icon.
Called from a native console, the platforms uniformly behave identically whether tclsh is called with or without a script as an argument. (Note question [L1 ] about windows tclsh misbehaving when run under third-party console.)
Under Windows, tclsh can be started from outside a console window, while linux/unix don't allow this, unless tclsh is opened with a script containing a 'package require Tk'. In MacOS X, tclsh is not an application, and thus cannot be started as such (double-clicking icon raises dialog "please locate application to open tclsh with").
When starting Tcl via wish, major differences will occur:
Here, the behaviour differs through OS'es when invoked without argument: windows and MacOS X creates a Toplevel AND a console, Linux/unix only a toplevel.
Having stated this, it seems that the use of WISH should be deprecated. This would imply that "the" simple way to invoke an interactive console in scripts running under Windows should be deprecated, too (i.e. the console command).
(These ideas are noted without commenting them in terms of value)
Idea 2 might be problematic, because the native shell is still active while processing tclsh + argument. But perhaps, a way can be found. However, for some system constellations this idea is even very valuable. E.g. in systems with a console device separated from a graphics device. Example: Embedded systems where a Tk app should start automatically after power-up. A remote console via serial port allows hooking in a running application when necessary. Without forcing interactive mode, remote introspection is possible only by killing the Tk-app, and then start it in two steps: tclsh + source xxx.
(further comments and ideas are welcome)