Re: [AD] set_config_file jumping around on OS X bundles

[Grzegorz Adam Hankiewicz <gradha@xxxxxxxxxx>]

On 2005-08-21, Elias Pschernig <elias@xxxxxxxxxx> wrote:
> Does override_config_file work under OSX? Under linux, it is best
> to never call set_config_file (since the /etc/allegro.cfg may have
> vital driver information for Allegro to start up at all). So I
> prefer to just use override_config_file on a game specific file
> [...]

And there is where Allegro's ship starts to sink. The so claimed
cross platform compatibility goes away if you need to start putting
conditional code to detect platforms (either through
#ifdefs or runtime checks).

I would prefer to have set_config_file do different things on
different platforms if necessary, in such a way that user code
only makes that one call and doesn't bother if the "brains" behind
Allegro decided that it stores the config file here or there,
as long as it is sensible for that platform.

Now back to the OSX platform, any nice ideas on what to do with
configuration files?