Talk:CE CHECK

Re ''Note that the VISA classes further utilize some CE-internal XDM-specific utility services (i.e. XdmUtils_ APIs) to do common tests. The sources for these utility classes are distributed with the Codec Engine releases if you want to explore them further. Further note that these XdmUtils_ APIs are considered internal APIs and therefore subject to change without notice''...

How can non-VISA skeletons/codecs use checked builds in such a case? i.e. how could a codec extending e.g. IUNIVERSAL add checked builds code?


 * non-VISA classes (that does not include IUNIVERSAL codecs) provide their own APIs/stubs/skels, and can call  to determine whether the user enabled checking.  They can then add whatever checking makes sense for their class of algorithm.  For example, in the CE example scale extension API, it could check that the buffers are "correctly formed" (perhaps re-using   APIs).
 * As far as IUNIVERSAL algs, those are loosely a "VISA class" as the interface is defined by XDM and supported by Codec Engine. In that particular case, IUNIVERSAL doesn't know what's 'correct' or not, so alg-specific checking is not supported.  As with other VISA APIs, the system integrator can plug in their own stubs/skels that include checking, but it's not provided out of the box.
 * If this is a common customer request, CE could perhaps add something like a "configurable checked callback" fxn that could be configured and called... but there hasn't been significant customer interest in this to date.
 * ChrisRing 15:03, 9 February 2009 (MST)