but now a front-end that wants to build against sane1.0 has to define these new macros itself, making portable front-end becomes harder?
allan On Mon, Feb 18, 2008 at 2:38 PM, Alessandro Zummo <alessandro.zummo at towertech.it> wrote: > > > An 1.1 compliant frontend should: > > 1) check for sane version >= 1.1 (a macro will be provided) > > 2) call sane_control_option > > int supported_version = SOMEMACRO(1,1); > > sane_control_option(handle, 0, SANE_ACTION_XXXX, &supported_version, > NULL); > > 3) the backend can then expose sane 1.1 features. > > I can check every backend driver to see if they can handle > a previously unknown SANE_ACTION_XXX and eventually fix them. > > > A frontend that declares itself 1.1 capable should be able > to handle unknown frame formats and, generally, be able > to correctly use the default: label of any switch statement > to handle an unknown condition. > > Especially when dealing with enums, it is a good practice > to not assume that an enum will always have a fixed amount > of entries. > > -- > > Best regards, > > Alessandro Zummo, > Tower Technologies - Torino, Italy > > http://www.towertech.it > > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org > -- "The truth is an offense, but not a sin"
