17 Mar
2007
17 Mar
'07
12:26 a.m.
"Jack Unrue" <jdunrue@gmail.com> writes:
So I can see why DEFAULT-ENCODING is returning NIL. Before I head over to clisp-devel and ask about this, I just wanted to see whether this situation surprises anyone here, or if you think it might be a CLISP build configuration issue (which would be funny because I'm one of the MingW package maintainers), or ???
Hmm, it's somewhat strange, I guess. BTW, should we worry about line terminator conversions?
This is on WinXP SP2, CLISP 2.41 (mingw special) with nothing related to encoding for command-line arguments.
I've applied a fix and a regression test for this. Should work now, though I haven't tested on windows. Thanks for the bug report. -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/