Hi,
after the replacement of JIMTCL with the new version, the command
puts does not work as before.
It prints nothing in the telnet connection, while is still working in
the default console.
Looking at the code, the reason is that the new jimtcl only prints to stdout.
Of course, it's possible to
Hi,
after the replacement of JIMTCL with the new version, the command
puts does not work as before.
It prints nothing in the telnet connection, while is still working in
the default console.
Looking at the code, the reason is that the new jimtcl only prints to stdout.
Of course, it's possible
This patch is good !
The use of echo is much better than puts by definition.
Does this mean you tested it?
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
On 08/11/2010, at 7:46 PM, Antonio Borneo wrote:
Hi,
after the replacement of JIMTCL with the new version, the command
puts does not work as before.
It prints nothing in the telnet connection, while is still working in
the default console.
Looking at the code, the reason is that the new
On Tue, Nov 9, 2010 at 7:08 AM, Steve Bennett ste...@workware.net.au wrote:
Probably it is a good idea to use echo everywhere for consistency,
but you could simply redefine puts in terms of echo.
Hi Steve,
overriding puts is the simpler way to avoid replacing all the tcl scripts.
I have to
Probably it is a good idea to use echo everywhere for consistency,
but you could simply redefine puts in terms of echo.
proc puts {args} {
tailcall echo {*}$args
}
That could work, but I don't want to call something puts
when it's not. Did you ever try typing on a French keyboard
when
On 09/11/2010, at 9:55 AM, Antonio Borneo wrote:
On Tue, Nov 9, 2010 at 7:08 AM, Steve Bennett ste...@workware.net.au wrote:
Probably it is a good idea to use echo everywhere for consistency,
but you could simply redefine puts in terms of echo.
Hi Steve,
overriding puts is the simpler way
