Hi, I want to know how I can keep reading from the same position over and over. Currently my program uses fgetc(* FILE) but it by default will advance the pointer to the next position. Is there another fFunction that helps you choose the position of the pointer in the text file. Thanks.
-V
fseek.
Why would one want to read from the same position again and again?
Bayint Naung beat me to the question...Originally Posted by nndhawan
But does it not strike you as a good idea to take that one bit of file, store it in a variable (in memory) and use the variable rather than pounding your hard disk to death?
What does it matter why? How can I do it?
Right now I have to keep opening and closing my File stream to reset the pointer which sucks and is way worse then just being able to decrement the pointer one time. Any good ideas?
Is there other operations that give you the actual memory location of the file? Either way the reason why is cause I'm reading a gpio port found in /sys/class/gpio/ and want to be able to constantly check what value it is.
Gee I dunno... maybe I cared enough to not want you to get stuck replacing a disk drive....
Silly me!
First is the stream seekable?Right now I have to keep opening and closing my File stream to reset the pointer which sucks and is way worse then just being able to decrement the pointer one time. Any good ideas?
Is there other operations that give you the actual memory location of the file? Either way the reason why is cause I'm reading a gpio port found in /sys/class/gpio/ and want to be able to constantly check what value it is.
If so look into using fread(string,blocksize,1,file) and fseek(file, -blocksize, SEEK_CUR).
Most non seekable streams will simply deliver the next available block with fread(), fgets() etc. with no need to close open etc between reads.
Last edited by CommonTater; 04-04-2011 at 05:45 PM.
We ask why, because people often come in here and ask, "Where can I get a gun?" We tell them where to get a gun -- they point it at their foot and pull the trigger
In other words, we want to know more about the problem, not your (assumed) solution to the problem. It's more helpful to you in the long run, and it saves us from feeling guilty about guiding you off the edge of a cliff.
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
