Re: [AD] standard path updates |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Thu, Jan 6, 2011 at 6:52 PM, Thomas Fjellstrom
<tfjellstrom@xxxxxxxxxx> wrote:
> That kind of defeats the entire purpose behind the swapable vfs setup. If
> you're using a separate VFS you really aught to make sure stuff is visible. Its
> something you should do consciously.
>
Whether or not a VFS falls back gracefully to stdio is up to the
programmer who writes it. If Allegro knows it must transparently open
up a local file, then it should explicitly use stdio. Allegro should
only use the VFS whenever the user expects that a file is being
accessed (loading images, config files, etc); but that's not happening
here.
Locating a system directory should technically be a system API call,
but apparently no such thing commonly exists in Linux. (At least, it
doesn't look like libxdg-basedir does this particular thing.) Linux
should work just like OS X or Windows, where the VFS plays no role in
locating the standard paths.
It would only makes sense for a VFS to alter the behavior of
al_get_standard_path if there was a ALLEGRO_FS_INTERFACE hook that it
could use to intercept calls to it. But I'm not sure such a thing
would even be useful.
--
Matthew Leverton