On Fri, Jan 26, 2018 at 1:41 PM, Peter Da Silva < peter.dasi...@flightaware.com> wr
> On 1/26/18, 1:37 PM, "sqlite-users on behalf of J Decker" < > sqlite-users-boun...@mailinglists.sqlite.org on behalf of d3c...@gmail.com> > wrote: > > doesn't get 26 either. 0x1a > > 26 isn't EOF, it's SUB (substitute). It was used to represent > untranslatable characters when converting (for example) EBCDIC to ASCII. > In the distant past (CP/M-80), the filesystem meta data did not include the actual _length_ of the data for a text data file. The I/O was done in sectors. The CP/M-80 system, by convention, used 0x1A (26) and an "logical EOF" indication and the C routines would detect it and report EOF. MS-DOS basically didthe same thing, for compatibility reasons. I am not sure, but I think that Windows still does this. A quick test with the command "type x.txt" where "x.txt" contained "abc~def" (where ~ is standing in for 0x1a) resulted in my seeing "abc". But "notepad x.txt" shows "abc def". So I guess it depends on how old the Windows app is. -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
