[sane-devel] [RFC] how to enable 1.1 features

[m. allan noah]

On Thu, Feb 28, 2008 at 4:29 AM, Alessandro Zummo
<azummo-lists at towertech.it> wrote:
> On Thu, 28 Feb 2008 08:43:26 +0900
>  Olaf Meeuwissen <olaf.meeuwissen at avasys.jp> wrote:
>
>  > Alessandro Zummo <azummo-lists at towertech.it> writes:
>  >
>  > >   please see the attached patch regarding my proposal
>  > >  for a safe enabling of 1.1 features in the backends.
>  >
>

in the fujitsu backend, i previously had added a 'compression' option
with the description warning of possible front-end incompatibility,
and the default setting to not compress. i feel this is sufficient,
because it requires no changes at all to a well-written frontend.

but, if you really want to protect this behaviour by requiring
'behind-the-scenes' frontend action, i would rather see a well-known
option with its caps flags set to make them invisible. i think
extending that flag (if required) is safer than adding macros or
extending enums, because '==' tests are done on the caps instead of
switch/case statements.

i would also rather see this well-known option be named by the feature
it implements, instead of a version name. By that means, a backend can
add support for something particular, and a frontend can enable
something particular.

allan
-- 
"The truth is an offense, but not a sin"