On 28 Aug 2010, at 12:15, Martin wrote: > On 28/08/2010 10:59, Jonas Maebe wrote: >> On 28 Aug 2010, at 01:07, Martin wrote: >>> But *if* fpc does lock the fpc.cfg file exclusively ( for a very short time >>> only, e.g. just open+lock, read, close), then there is the slim chance of a >>> conflict, and this error could be explained. >> FPC opens it as a regular text file using a regular assign/reset. I don't >> think that will result in exclusive access. It also checks for its existence >> using sysutils.fileexists, but I doubt that one asks for exclusive access >> either. > > Afaik uing assign/reset using exclusive lock on windows.
I thought that was only for regular files, not for text files (since if you open a regular file using reset, you can still write to it, while that's not the case for text files). Jonas _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
