bugs buggy schreef: > Ok, the issue is, that we open the music file. (in base/music). > Then we want to remove base, since we are going to play a MP game. > But we can't since we still have a open file handle. > This leaves it in the physfs search path, and causes us issues.
I actually consider this an API bug. To compare with the way how Linux (and possibly other *nixes as well) handles files. When on Linux you have a file opened (e.g. for reading/writing/etc.) and at the same time another process (or perhaps the same) removes the file, all that happens is that the file cannot be opened or seen anymore (in directory listings). The actual removal of the file is delayed until *all* handles to that file are closed. I would actually prefer for something similar to happen in PhysFS. I.e. when we remove a dir/archive from the *search*path*, that that's all that's done: preventing file new searches from happening in that dir/archive. I actually consider it an API bug of PhysFS that it simply continues to search in that dir/archive until all files are closed (and the removal is attempted again). -- Giel
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
