[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Ben Davis:
> On Tuesday 16 March 2004 07:01, aj wrote:
>> one argument i have heard is that the new behaviour will do-its-thang for
>> already compiled apps, but just how many apps will be released on the
>> 4.1.13 lib built from old source code ? surely we could remove the
>> name yeild_timeslice so anyone re-compiling older source for the 4.1.13
>> lib will be forced to change the source to either sleep_minimum_timeslice()
>> [or whatever the new names are].
> Say User 1 has used Allegro 4.0.3 to write a game, and has released all source
> code. User 2 is new to Allegro, installs Allegro 4.1.13, downloads User 1's
> game, and tries to compile it. He gets errors, and because Allegro is
> unfamiliar, doesn't feel able to fix them. He gives up.
> No thanks.
User 1 shouldn't assume his code will work with any newer version of Allegro,
though. Otherwise, how can Allegro ever be improved? Maybe yield_timeslice()
could be deprecated; just like the old text API...
Kind regards,
Daniel Schlyder
--
http://bitblaze.com/