[physfs] request for 'openReadWrite'

Jeremy jswigart at gmail.com
Sat Apr 25 13:21:54 EDT 2009

Yea there's really no reason why this sort of functionality shouldn't be
available. Worst case it could fail on archived files.

On Sat, Apr 25, 2009 at 3:23 AM, Matheus Izvekov <mizvekov at gmail.com> wrote:

> > Since the library can't write to files inside archives at the moment
> > anyway, I don't think it's fair to expect such functionality when
> > opening a file for both reading and writing either.
> Well this argument fails to account for the fact that physfs separates
> writable files from everything else. Also, openAppend already violates
> this.
> > The proposed solution would be better to implement in your application
> > rather than inside PhysFS. We do something similar with music files
> > currently, because SDL_mixer can only stream from physical files. So
> > if a music file is inside an archive, we temporarily extract it to the
> > writable directory.
> >
> I don't see how would that apply to me. If I can't have rw files, the
> best solution after that would be to keep the file path around instead
> of just the file handle, and open it for either read or write depending
> on the operation, and then close it shortly after. Performance issues
> and memory fragmentation aside, this is very unpleasant to maintain, and
> I would much rather have platform dependance.
> > Regards,
> > Bjørn
> > _______________________________________________
> > physfs mailing list
> > physfs at icculus.org
> > http://icculus.org/mailman/listinfo/physfs
> _______________________________________________
> physfs mailing list
> physfs at icculus.org
> http://icculus.org/mailman/listinfo/physfs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/physfs/attachments/20090425/b9a54016/attachment.htm>

More information about the physfs mailing list