Ah yes, the old \r\n hack rears its ugly head again. The main problem
here is that the "fix" in Jacl 1.1 was really just an ugly hack that
gave the false impression that things were working correctly. The
real problem here is that the Jacl "channel" drivers do not take
\r\n into account. To really
I am sourcing a script that has the following lines in it. Whenever I
source it, it gives an error. I am
using Jacl 1.2.5. This used to work in Jacl 1.1.1.
set x 3
if {$x == 3} \
{
puts $x
} \
else \
{
puts "Bad"
}
The following is the error information:
%source
"D:\\TestBench\\ClearCa
