[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Thu, Mar 18, 2004 at 01:26:13AM +0100, Daniel Schlyder wrote:
> User 1 shouldn't assume his code will work with any newer version of Allegro,
> though.
Unless, of course, the docs state that API compatibility between the current
version of Allegro and future versions is guarenteed. Note that there are some
minor API breaks between 4.0 and 4.1, but those are modest and not s severe
as a function being deleted altogether.
What a user should not assume is that code will work with an older version
of Allegro. Newer versions, certainly on the stable branch, should be API
compatible, or provide a compatibility layer.
If the application requires a specific version (eg, 4.0) then the documentation
that comes with the project should mention that and there should be compile
(or configure) time checks for the Allegro version.
> Otherwise, how can Allegro ever be improved?
By providing backward compatibility layers (see the
allegro/include/allegro/alcompat.h header file) that can optionally be disabled.
> Maybe yield_timeslice()
> could be deprecated; just like the old text API...
Yes, that would be possible.
Evert