eugene_shebeko wrote: > > I see that idea that tab could be only read or only write cross over > all source code of mitab :) What the reason of such design? > Suppose it's really hard to imlement random write access to .tab file, > due to complex .tab structure. Is it hard to implement append to tab? >
The library is designed so that it could eventually support random read/write access some day (hence all the checks for read-onle/write-only everywhere in the code), but random access was never implemented simply because that would have added a non trivial amount of work, and that was not a priority at the time... and never has been a priority for me or any paying client since then. > How do you think, how many time need to add random write access to tab > file? > What main changes that I need to do in mitab? > The changes would be to go to all the functions that read or write to the files and make sure random-access is properly supported. e.g. making sure all write buffers (blocks kept in memory in write mode) are flushed if a read operation is called, making sure all the required write-mode data structures are loaded/populated before any write operation, etc. 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/
