Forum .LRN Q&A: Re: slash and tcl

Collapse
12: Re: slash and tcl (response to 1)
Posted by Don Baccus on
This won't help you today but AOLserver 4.0 will shortly (in the next couple of months, I believe) support Win32 natively.

Which means it will treat thost nasty <cr><lf> pairs that windows uses instead of the Unix world's <lf> as a single character, fixing this problem.

I believe Tcl's interpreting the <cr> as whitespace because it's running as a Unix program (under Cygwin, I imagine) not as a Win32 program, and has no way of knowing that you've in essence converted the source file to Windows.

Search for Jamie Rassmussen - he's our most experienced Win32 person (he's doing the AOLserver 4.0 Win32 support) and he can probably tell you the simplest way to make sure you get the files downloaded to your system in a way that the current Tcl environment will support.