"Brian S. Julin" wrote: > Getting this into an API that anyone is going to want to use is a worthy > program design challenge :-) hear, hear. seriously, this is precisely why I'm against exposing these 'features' to the API user. The API should be abstract, always having the potential use cases in mind. It's then the task of the programmer to map that to whatever is available in h/w, i.e. there could be different polymorphic implementations available which care about that. Stefan
- Re: does this look acceptable Lee Brown
- Re: does this look acceptable Lee Brown
- Re: does this look acceptable Stefan Seefeld
- Re: does this look acceptable John McCutchan
- Re: does this look acceptable Andreas Beck
- Re: does this look acceptable Lee Brown
- Re: does this look acceptable Jon M. Taylor
- Re: does this look acceptable Brian S. Julin
- Re: does this look acceptable John McCutchan
- Re: does this look acceptable Lee Brown
- Re: does this look acceptable Stefan Seefeld
- Re: does this look acceptable Andreas Beck
- Re: does this look acceptable Jon M. Taylor
- Re: does this look acceptable Stefan Seefeld
- Re: does this look acceptable Andreas Beck
- Re: does this look acceptable Lee Brown
- Re: does this look acceptable Andreas Beck
- Re: does this look acceptable Lee Brown
- LibOVL and LibBlit (was: Re: does this look acceptabl... Christoph Egger
- LibOVL, LibBlt and LibBSE Christoph Egger
