2009/11/16 Andreas Raab andreas.raab@gmx.de:
Nicolas Cellier wrote:
1] ABOUT RECENT CHANGES IN TRUNK:
[...]
- Since It is far more simple to handle the zoo of line delimiters in
Kernel (CompositionScanner / DispalyScanner / String / Stream)
Hey, you beat me to it ;-) I had looked at this a little while ago but missed the subtlety in CompositionScanner and friends. Great job!
2] IMPORTANT NOTE AND QUESTION:
SocketStream>>nextLine does insist on finding a CR-LF pair. This is used in some major protocols. But I find this abusive, and would like to change the default behavior to that of Stream. This would be a nice property that a SocketStream behaves like a FileStream or an ExternalStream. Should I proceed ?
I don't really care as long as the default behavior is strict (i.e., no magic detection of line ends). OTOH, I'm not sure how useful it would be; there is something to be said for strict handling in network protocols.
There is a #nextLineCrLf for strict requirements, but of course that would put the pressure on package maintainers...
Cheers, - Andreas