| Re: [AD] set_config_file jumping around on OS X bundles |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Monday 22 August 2005 21:23, Matthew Leverton wrote:
> That breaks backward compatibility? If so, could we agree on a dummy
> entry that's not documented yet so we don't have to wait three or four
> years for a proper fix to appear on a stable version?
I'd rather not. I don't think there's much difference in adding a null
vtable entry and adding one with functions filled in.
We can work around it for now in 4.2 with #ifdef
ALLEGRO_MACOSX/ALLEGRO_WINDOWS/WHATEVER. It's not pretty, but it'll have
to do. We basically did the same already for the Mode-X stuff.
Just mark it as /* TODO: add proper vtable function for this */
Evert