Should BufRead::lines() et al recognize more than just LF?

[llogiq]

My proposal was not having the same function implemented differently per system, but have a system-specific function in each system’s os::* crate. The global io-function should then be as system-agnostic as possible.

[SimonSapin]

Do you mean std::os::unix and std::os::windows? These are only available on the corresponding platform, while there is no reason to limit availability of any line-break style. For example, CR LF is used on Windows but also in HTTP.

[stej]

Any progress here? I don’t see any conclusion. I read logs made on windows and have to deal with CRLF somehow. So is the current solution the same - using ::lines() and trim somehow the trailing CR?

[bluss]

We are trying to decide what to do right now (this week), either change lines() to trim \r too, or add another method proposed to be called .lines_any() that does that.

[troplin]

That said, I don’t see why that is a major issue if in the specific case of a state flag saying I just read \r as an end-of-line character, so if the next character is \n then ignore it.

This is how Java seems to handle it btw. But the flag is in the BufferedReader class, not int the Std-Input stream itself.

[system]

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.