C Language, reading text files in binary mode

reading text files in binary mode

Author	Message
evilscient.. #1 / 8	reading text files in binary mode Does opening a text file in binary mode give you a more accurate "picture" of the file. I am opening a file in "r" mode and there seems to be some garbage characters at the end of the file that are screwing up my algorithm big time. If so, can someone point me in the right direction on how this is done? Thanks, evil Sent via Deja.com http://www.--*.com/ Before you buy.
Wed, 24 Apr 2002 03:00:00 GMT

evilscient.. #2 / 8	reading text files in binary mode Quote: > / Does opening a text file in binary mode give you a more accurate > / "picture" of the file. I am opening a file in "r" mode and there seems > Depending on your system, text i/o can map the new line character '\n' in > your source into various other representations like <LF>, <CR>, <CR><LF>, > <US>, etc > / If so, can someone point me in the right direction on how this is done? > You can try open mode "rb". That's it? I don't have to make any other changes in my code? evil Sent via Deja.com http://www.deja.com/ Before you buy.
Thu, 25 Apr 2002 03:00:00 GMT

Gergo Bara #3 / 8	reading text files in binary mode Quote: > > / Does opening a text file in binary mode give you a more accurate > > / "picture" of the file. I am opening a file in "r" mode and there [snip] > > You can try open mode "rb". > That's it? I don't have to make any other changes in my code? That's basically it. Read it byte by byte into unsigned chars and print their hex/octal/decimal representations. Gergo -- Make no little plans; they have no magic to stir men's {filter}. -- Daniel Hudson Burnham GU d- s:+ a--- C++>$ UL+++ P>++ L+++ E>++ W+ N++ o? K- w--- !O !M !V PS+ PE+ Y+ PGP+ t* 5+ X- R>+ tv++ b+>+++ DI+ D+ G>++ e* h! !r !y+
Thu, 25 Apr 2002 03:00:00 GMT

Homer Simpso #4 / 8	reading text files in binary mode Gergo Barany a crit dans le message ... Quote: >> > / Does opening a text file in binary mode give you a more accurate >> > / "picture" of the file. I am opening a file in "r" mode and there >[snip] >> > You can try open mode "rb". >> That's it? I don't have to make any other changes in my code? >That's basically it. Read it byte by byte into unsigned chars and print >their hex/octal/decimal representations. Not an unsigned char but an int rather, because the value of EOF is by definition a negative int and have to be tested after any read, and not to be processed like a data. -- HS C- FAQ: http://www.eskimo.com/~scs/C-faq/top.html About gets() and fflush(stdin) : - "Even Buffy cannot slay the resulting RhinoDaemons." Martin Ambuhl clc.
Thu, 25 Apr 2002 03:00:00 GMT

Gergo Bara #5 / 8	reading text files in binary mode Quote: > Gergo Barany a crit dans le message ... > >> > / Does opening a text file in binary mode give you a more accurate > >> > / "picture" of the file. I am opening a file in "r" mode and there > >[snip] > >> > You can try open mode "rb". > >> That's it? I don't have to make any other changes in my code? > >That's basically it. Read it byte by byte into unsigned chars and print > >their hex/octal/decimal representations. > Not an unsigned char but an int rather, because the value of EOF is by > definition a negative int and have to be tested after any read, and not to > be processed like a data. I was thinking of reading the unsigned chars and checking feof() after each read. But your way is just as good (or even better). Gergo -- "Because he's a character who's looking for his own identity, [He-Man is] an interesting role for an actor." -- Dolph Lundgren, "actor" GU d- s:+ a--- C++>$ UL+++ P>++ L+++ E>++ W+ N++ o? K- w--- !O !M !V PS+ PE+ Y+ PGP+ t* 5+ X- R>+ tv++ b+>+++ DI+ D+ G>++ e* h! !r !y+
Thu, 25 Apr 2002 03:00:00 GMT

i.. #6 / 8	reading text files in binary mode Quote: > > Not an unsigned char but an int rather, because the value of EOF is by > > definition a negative int and have to be tested after any read, and not to > > be processed like a data. > I was thinking of reading the unsigned chars and checking feof() after > each read. But your way is just as good (or even better). Much better; feof() doesn't get set until after you've read one character beyond the end of the file, not as you read the last character. This, btw, is in the FAQ. Richard
Fri, 26 Apr 2002 03:00:00 GMT

Gergo Bara #7 / 8	reading text files in binary mode Quote: > > > Not an unsigned char but an int rather, because the value of EOF is by > > > definition a negative int and have to be tested after any read, and not to > > > be processed like a data. > > I was thinking of reading the unsigned chars and checking feof() after > > each read. But your way is just as good (or even better). > Much better; feof() doesn't get set until after you've read one > character beyond the end of the file, not as you read the > last character. This, btw, is in the FAQ. I am aware of that. This code: unsigned char c; c = getchar(); while(!feof(stdin)) { printf("%x ", c); c = getchar(); Quote: } is clumsy, but it works. Gergo -- The goys have proven the following theorem... -- Physicist John von Neumann, at the start of a classroom lecture. GU d- s:+ a--- C++>$ UL+++ P>++ L+++ E>++ W+ N++ o? K- w--- !O !M !V PS+ PE+ Y+ PGP+ t* 5+ X- R>+ tv++ b+>+++ DI+ D+ G>++ e* h! !r !y+
Fri, 26 Apr 2002 03:00:00 GMT

Page 1 of 1

[ 8 post ]