If I were, in the main() function, to open a file, then kickoff a number of threads that would all access the file with each thread reading in a line each using fgets (which says that it is thread safe if I am reading the man page correctly), then each thread will be able to do this without tripping over each other, correct?
Thanks
I guess so, if it says that it is thread-safe.
Though which thread gets which line is probably more interesting...
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
In this case it doesnt matter because each line is a single record, and no two lines are dependant on each other, so each line can be processed independently to any other. I wanted to check that thread safe meant that no two threads could be calling fgets at the same time. I guess that it has some sort of atomic queueing mechanism in there.
I looked at the source in the MS library a while back, and they have a mutex to prevent more than one thread inside the file function at any time - it is one lock per file, so if you open multiple files, they are not blocking on each other. Of course, I don't know if the C-library is implemented the same way - but I expect that to be the case.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
