Re: EOF detection

From: Henning Meier-Geinitz (henning@meier-geinitz.de)
Date: Tue May 08 2001 - 11:21:26 PDT

  • Next message: Henning Meier-Geinitz: "Re: Problems with 2.4.4 kernel and scanning"

    Hi,

    On Tue, May 08, 2001 at 06:01:47PM +0200, Oliver Rauch wrote:
    > > "The number of bytes returned is stored in *len. A backend must set
    > > this to zero when the call fails (i.e., when a status other
    > > than SANE_STATUS_GOOD is returned)"
    > >
    > > So you can't return data if you don't return SANE_STATUS_GOOD.
    >
    > Yes, but you also can argue that SANE_STATUS_EOF is not a failure,
    > only the info that there is no more data than returned by
    > this sane_read command.

    Depends on what "i.e." is supposed to mean.

    > It does not hurt to mention it explictly.

    I think that's more clear:

      The number of bytes returned is stored in *len. A backend must set
      this to zero when a status other than SANE_STATUS_GOOD is returned.

    Is this clear enough or should we add another sentence concerning
    SANE_STATUS_EOF (in addition to "SANE_STATUS_EOF: No more data is
    available for the current frame.")?

    Bye,
      Henning
      

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
    



    This archive was generated by hypermail 2b29 : Tue May 08 2001 - 11:10:45 PDT