On Fri, Jan 26, 2018 at 10:22 AM, Peter Da Silva < peter.dasi...@flightaware.com> wrote:
> On 1/26/18, 12:12 PM, "sqlite-users on behalf of Keith Medcalf" < > sqlite-users-boun...@mailinglists.sqlite.org on behalf of > kmedc...@dessus.com> wrote: > > Actually, EOF (0xFF) *is* part of a text file, and is the byte in an > ASCII byte-stream that indicates end-of-file. In the "old days" the bytes > following the last-byte in a stream and the end of a storage block > (sector/cluster/track/cylinder, what have you) were padded with 0xFF so > you knew you were past the end-of-the-file when you were reading it. > > Oh, I remember the messes that existed before stream files became the > norm. But messes they were, and there's no more reason to support them in a > Unicode file than there is to support FIELDDATA format. > > And if you're going to talk about the block file and paper tape era, don't > forget that FF also meant a deleted character and should be skipped without > being counted or accounted for. > > ctrl-z was end of file text character in DOS (wrote char 26; not FF) EOF is returned as -1 not 0xFF (although signed char looks really similar) the character 0xFF is 0xC3 0xBF nof 0xFF. > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
