[physfs] Multiple contexts in one process

[Francesco Bertolaccini]

I don't have a specific use case right now, but I can imagine it being very
useful if, for example, a game wants to use PhysFS both for general IO and
for sandboxing stuff like user mods, so that the engine has access to the
whole tree while mods are only allowed to look at their own data

On Fri, May 18, 2018 at 9:26 AM, Sherief Farouk <sherief.personal at gmail.com>
wrote:

> That's how this branch currently implements it - so far everything is
> backward compatible, I was just surprised by Ryan's comment and was
> wondering whether he'd ever consider a non-backwards-compatible future
> path. I currently have no plans to suggest changes that break backwards
> compatibility - if it comes to that I think a fork would be better. I'm
> curious to hear whether you have a use case for this feature.
>
> On Thu, May 17, 2018 at 9:33 PM Francesco Bertolaccini <
> bertolaccinifrancesco at gmail.com> wrote:
>
>> What if backwards compatibility was provided by keeping a default global
>> context that can be accessed through the current API, but actually acts as
>> a thin wrapper around the new reentrant interface?
>>
>> Il ven 18 mag 2018, 06:25 Ryan C. Gordon <icculus at icculus.org> ha
>> scritto:
>>
>>>
>>> > At what point would you consider giving a solid yes / no to whether
>>> this
>>> > is welcome as a future feature to PhysFS? If I don't need to maintain
>>> > backwards compatibility I can move faster and implement a leaner API,
>>> > though a complete fork is something I usually prefer to keep as a last
>>> > resort.
>>>
>>> I'm definitely not interested in breaking backwards compatibility, and
>>> I'm not sure I'm interested in the feature in general, either.
>>>
>>> --ryan.
>>>
>>>
>>> _______________________________________________
>>> 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/20180518/2c1466ef/attachment.html>