On (2003/02/05 13:19), a.piesk@??? wrote:
> > Why did you change exiscan to start failing when no output is received
> > >from a command-line scanner?
>
> i did the change. the reason:
>
> a scanner could die without returning any output. scanner's malfunction or
> segfault or whatever.
> how should that be handled? the av_cmdline stuff must be as generic as
> possible. so i think, treating no output as error is the safest way.
>
> maybe you know a better solution i'm not aware of. suggestions?
When you're trying to craft a tool that works for screws and nails,
you need to provide a hard, flat, heavy bit at one end, and a thin,
sharp angular bit at the other.
(The behaviour should be conditional on an option that can be set by the
administrator, of course). :-)
