Fergus Henderson wrote:
> There are lots of examples where this sort of things causes real
> problems in practice. If you think this is not a problem in the
> real world then I suggest you read the archives [...]
OK, I'll rephrase my opinion a little bit: Thanks to the "wise"
decision to use multi-byte printer codes for the single semantic
thing "my line ends here" on certain platforms, we are forced to
distinguish between the representation level and the application
level. IMHO seek/tell belong to the lower (i.e. representation)
level, consequently the CR/LF vs LF is a non-issue here. Lseek's
manual pages tell me something about a *byte* offset, not a
*character* offset.
Related points would be: What does hGetChar exactly mean in the
presence of Unicode/UTF-8/... and random access?
Cheers,
Sven
--
Sven Panne Tel.: +49/89/2178-2235
LMU, Institut fuer Informatik FAX : +49/89/2178-2211
LFE Programmier- und Modellierungssprachen Oettingenstr. 67
mailto:[EMAIL PROTECTED] D-80538 Muenchen
http://www.informatik.uni-muenchen.de/~Sven.Panne
