| Re: [AD] dll binary compatibility maintenance. |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Eric Botcazou <ebotcazou@xxxxxxxxxx> wrote:
> Is that stuff really needed ? I think we should make a clear requirement
of
> not removing any symbol between binary compatible versions: 4.0.0, 4.0.1
and
> so on.
it's in CVS now. if you have a better idea, then i'd be interested to hear
about it. i think it is better to have the removed symbols in
src/win/compat.c since it is only needed for windows and there's a
dll_error() function for handling cases where a program calls a removed
function instead of just pretending everything is ok. it works, i did test
it before i committed it of course. IMHO allegro programmers should be free
to change around the internals any way they like but be careful when it
comes to do API changes. we can remake the dll definition list and clear
compat.c when 4.0 gets released.
-henrik