Andrew wrote: > > I am using IMapInfoFile (I am compiling the source into my executable > not linking against the library) and I was wondering if anybody has a > list of the member functions that write to disk, that way I can > restrict my locks to specific areas vice having to lock during the > entire operation. >
I don't have such a list, you'd have to look through the code to find them, or perhaps you could try putting your lock around the TABRawBinBlock::CommitToFile() method. I think all writes to the .MAP file go through that (but I could be wrong). But what are you trying to do exactly with the locks? The only use I can think of is that you are trying to have a multithread app with multiple threads operating on the same file, some in read mode and some in write mode? FYI, puting mutexes around the functions that write to the file would not be enough to be able to write to and read from the same file because the header block is only written when the file is closed for instance, and even when other blocks are written I'm not sure that all the places that refer to the new data blocks are forced to disk until you close the dataset. HTH Daniel -- ------------------------------------------------------------ Daniel Morissette [EMAIL PROTECTED] DM Solutions Group http://www.dmsolutions.ca/ ------------------------------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/mitab/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
