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

[Evert Glebbeek <eglebbk@xxxxxxxxxx>]

> > > - Decide if this isn't a bit late to go into 4.2.0
> > 
> > In my opinion, it is. I think we're beyond the `add function to vtable'
> > stage.
> >
> As long as we are allowed to make this sort of change for 4.2.1, then
> I say it's too late.

Certainly not. Adding new vtable functions breaks binary compatibility on 
all platforms.

> > > - If yes, find a way what to do for 4.2.0 (some platform specific
> > >   set_config_file/override_config_file magic)
> > 
> Well, if we think that we are going to be improving it in the near
> future, I'm satisfied with leaving it as is, and just putting a
> warning in the documentation that says that you may not call
> set_config_file before allegro_init if your application is sitting in
> a OS X bundle.

I think a proper solution can only be found in the 4.3 branch. For the 4.2 
branch, Allegro most certainly should treat the bundled config file as a 
read-only file. It'll probably be a bit of a hack to make it do that 
properly though...

Evert