Uwe Bonnes wrote:
[snip]
> Just a remainder. \r\n vs pure \n might be another source of problems.
I am not sure whether I should take up this issue on the scanner side
because it is trivial to resolve by other means. Afterall, we are
compiling on unix-type machines, which have '\n' as standard. The only
valid reason would be to backport wrc to dos/win32 platforms, but I
haven't done that since (approx) version 1.0.0 anymore. If there are any
other compelling reasons to suppurt '\r\n', then I might reconsider.
Another issue here is the embedding of '\r\n' in resource strings. This
needs to be resolved if, and only if programs depend on them, which I am
not convinced of yet. I haven't seen many programs that have newlines in
them which aren't covered by single '\n'. I'll have to investigate a bit
more to get the full picture.
Greetings Bertho
