Major A schrieb:
> The SANE API is designed to be simple and portable, and any change
> towards object orientation or functional programming would only bloat
> it unnecessarily. Sorry, if you want to interface Scheme to SANE,
> you'll have to adapt to the way things are.
Well, changing the curren
> I don't think that network transparency introduces a problem for "user
> data" pointer sizes. Since Sane itself does not deal with this pointer,
> the net backend does not need to send and receive the correct value of
> this pointer to/from the Sane server. Instead, the net backend can use
>
> > A thin C interface layer could then use one callback dispatcher to
> > handle all C callbacks. The callback dispatcher could use stdarg.h
> > to process the other args or perhaps they could be passed to the
> > callback using a count and array.
>
> Well, maybe the other developers have more e
Hi,
I forgot to add:
On Sun, Jul 20, 2003 at 08:48:54AM -0400, Peter Santoro wrote:
> In the future, I would be happy to contribute a scheme->sane interface
> library to the sane project, but it sure would be nice if the sane api was
> more non-C friendly.
I don't want to discourage you: A sch
Hi,
On Sun, Jul 20, 2003 at 08:48:54AM -0400, Peter Santoro wrote:
> Although I have a number of years of experience programming C/C++/Java, I
> now prefer to use scheme for most of my programming. After briefly looking
> at the sane api, I noticed that callbacks are sometimes used.
The initial version of my based application (written in scheme) does not use
the sane api directly, but utilizes
scanimage and scanadf to perform scanning. In a future release, I would like
to use the sane api directly for better
control.
Although I have a number of years of experience progra
