Printable View
Hello ,
I was wondering something. Assume we have a text file which contains : " Hello I am me". We use fgetc(fp) and we get H character. Next time we use fgetc(fp) we get e character. Very Nice. But I am wondering how the program can keep last character we took in its mind. I mean how can the program keeps the character we are on in its mind?
Thank you for every response...
I don't understand the question really. Are you trying to store the characters somewhere? You could store each char into a char array, but that's what fgets() is for.
No not really , not that of a question. I'll try to explain again.
You know each time we use fgetc with the same file pointer , we reach the next character from the text file. I wonder how can the program do that , how can it change the character each time , how can it recall where we stopped last time?
Oh, that's internal implementation. Without launching into great detail, the FILE struct usually contains a buffer of chars read from the underlying file from the O/S. It also contains a char * that points to the exact position in that buffer where you're currently at. When you call fgetc() it returns the char located at the pointer, and then increments the pointer by one.
That is how I've seen it done, but those details are hidden from us and we can't assume anything about how they are done because they are done differently for each O/S and even up to a point for each compiler.
If you want to find out where you stopped, use ftell(), otherwise I have no idea what you're asking :)
On some systems you can even map a file to memory, and move around it as if it was as so, just remember that it's sometimes a stream and doesn't necessarily end.
This is probably more details than the original poster wanted to know, but essentialy somewhere low down in the filesystem, there is a counter/pointer to keep track of where in the file the last read ended (starting at zero when the file is opened for reading, normally). Reads, at this level are done in blocks (or multiples thereof). If a request from the user-level asks for less than a whole block, the read is "rounded up" to the block-size, and the whole block is kept in the buffer for that file - and when that is finished, the next block is read if there's more read requests.
In the upper level, there is also various counters and buffers to hold some of the data coming from the file - this is because it's relatively expensive to call the OS to read small blocks of data - so the C-library will ask for a bigger block and deliver data from that block as/when necessary, until it's needs more data from the OS and does another read request.
I hope this makes sense.
--
Mats