"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

Reply via email to