mizvekov at gmail.com
Thu Jan 28 00:53:17 EST 2010
On 00:17 Thu 28 Jan , Ryan C. Gordon wrote:
> >couldn't same/similar method be used for R/W? What are the issues?)
> Opening x.txt for read may be a different x.txt than you'd be
> opening for writing, as the write path and the search path are
> Also, I don't want to be responsible for defining the semantics:
> what state is the file left in between a read and a write, etc.
> physfs mailing list
> physfs at icculus.org
That's actually quite easy to define, if you have a function which opens
a file both for reading and writing. I provided a few simple choices of
semantics on the emails following my openReadWrite patch which I sent to this
list several months ago, and never heard back about it again.
If you don't want this, just say you don't, but please don't make these
excuses that it would be hard or messy to do.
More information about the physfs