sane-project-website/old-archive/1999-08/0294.html

69 wiersze
2.8 KiB
HTML

This file contains invisible Unicode characters!

This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.

<!-- received="Tue Aug 24 15:36:18 1999 PDT" -->
<!-- sent="Tue, 24 Aug 1999 23:42:24 +0100 (GMT)" -->
<!-- name="Nick Lamb" -->
<!-- email="njl98r@ecs.soton.ac.uk" -->
<!-- subject="Re: SANE V2" -->
<!-- id="" -->
<!-- inreplyto="37C2F28A.D496A065@wolfsburg.de" -->
<title>sane-devel: Re: SANE V2</title>
<h1>Re: SANE V2</h1>
<b>Nick Lamb</b> (<a href="mailto:njl98r@ecs.soton.ac.uk"><i>njl98r@ecs.soton.ac.uk</i></a>)<br>
<i>Tue, 24 Aug 1999 23:42:24 +0100 (GMT)</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#294">[ date ]</a><a href="index.html#294">[ thread ]</a><a href="subject.html#294">[ subject ]</a><a href="author.html#294">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0295.html">Jordi: "EPSON GT9000"</a>
<li> <b>Previous message:</b> <a href="0293.html">Nick Lamb: "Re: SANE V2"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
On Tue, 24 Aug 1999, Oliver Rauch wrote:<br>
<p>
<i>&gt; I see no advantage of using numbers for it, but it makes it much more</i><br>
<i>&gt; easy for the frontend programmers to support new formats and it is</i><br>
<i>&gt; much more easy to add new formats to the standard because you do</i><br>
<i>&gt; not need a new sane.h file.</i><br>
<p>
I still like numbers, not least because we'll have to keep them around<br>
anyway for compatability with SANE 1.0<br>
<p>
Also, Andreas is wrong to portray the enumerations as only having down<br>
sides. Look in your GIMP header files some time to see broken formats<br>
replaced by renaming the appropriate enums. This makes it possible for<br>
Gimp to be backwards compatible with buggy versions of Gimp (!)<br>
This mechanism has also been used by IJG libJPEG and by libTIFF<br>
<p>
Example for SANE<br>
<p>
Some time after SANE_FRAME_BLAH is established we discover that the<br>
existing backends and frontends have co-incidentally implemented<br>
the same wrong behaviour. We could then re-write all the software,<br>
and require users to upgrade immediately, or we could just do this:<br>
<p>
SANE_FRAME_BROKEN_BLAH = old value of SANE_FRAME_BLAH<br>
SANE_FRAME_BLAH = newly issued frame type number<br>
<p>
Which makes it possible to auto-detect broken frames from the old<br>
broken backends in a new frontend, and correct for it (if possible)<br>
or at least avoid nasty surprises.<br>
<p>
Nick.<br>
<p>
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0295.html">Jordi: "EPSON GT9000"</a>
<li> <b>Previous message:</b> <a href="0293.html">Nick Lamb: "Re: SANE V2"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>