Path: csiph.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c++ Subject: Re: getline() problem Date: Mon, 25 Apr 2022 10:19:36 -0700 Organization: None to speak of Lines: 24 Message-ID: <87o80paxnb.fsf@nosuchdomain.example.com> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="52797b55255e88ed2a58203b73d67c4b"; logging-data="12812"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19f3tFdy8Llo4C1aApMjoGE" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:Z1NWNLUuU6qeJUBRm0hM3AvPI6A= sha1:EPLZugWzR46Nz3TSj/bePCMobko= Xref: csiph.com comp.lang.c++:83743 Vir Campestris writes: [...] > Windows text files have 13,10 as a newline sequence, not just 10 as in > Linux etc. > > This dates back to at least CP/M where the byte stream in the file > exactly matched the one you would send to your CRT or printer, and a > line feed really did move the roller but not the print head. > > I have a vague feeling that Apple might use 10,13 - certainly I've met > it somewhere in the past. Versions of MacOS before version X (10) used CR as a line terminator. OS X, since it's Unix-based, uses LF. > The point of text mode is to allow a program to ignore these > differences by allowing the runtime to handle them. > > It's not 100%. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Working, but not speaking, for Philips void Void(void) { Void(); } /* The recursive call of the void */