[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Chris:
> When I came newly to Allegro, I would expect code that requires Allegro
> to work. Especially for new coders, library version differences don't
> register as potential problems, or ones you're willing ot work on to fix.
Yeah, I agree to an extent, I just hope that if Allegro 5 ever becomes a
reality, its feature set won't be dictated by a need to be backwards
compatible.
> Or yield_timeslice could continue to act as it did in 4.1.12 and
> earlier, with al_idle acting as rest(1). Both would behave differently
> so there wouldn't be any need to depricate anything. How about this:
> #define yield_timeslice() rest(0)
That won't work unless rest() is changed; it calls yield_timeslice() on some
platforms.
Kind regards,
Daniel Schlyder
--
http://bitblaze.com/