| Re: [AD] demo of new timer API (unix only) |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Evert Glebbeek wrote:
Cheers. I'll put up a newer version tonight as there's a thread-safety
bug in the previous version I uploaded. Silly Allegro calls
install_int/remove_int from inside interrupt callbacks...
I didn't experience any problems running your last version here. Everything
seems to be working fine here.
Well, here's the newer patch. Bug fixes & a little less code duplication.
http://members.ozadsl.com.au/~tjaden/a5/nu/nu-timer-api-20040819.tar.gz
I'm guessing that the old timer stuff
should eventually be moved to a compat.c compatibility file? Or may placed
in an src/compat subdirectory once there are more files for which backward
compatibility wrappers are needed?
src/compat sounds good. Unfortunately CVS doesn't understand renames, bah.
Oh, a question about threading: what was the concensus on exposing a
multi-threading API from Allegro?
Er, some for, some against :-)
As part of the new API, I'm fine with it. But any cross-platform thread
API is going to be very common denominator -- useful, sure, but we must
allow room for users to use native thread APIs instead. Low coupling
between various parts of the API is a good goal anyway.
Peter
PS. I started a little internal thread API as part of the timer patch.