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

84 wiersze
3.6 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="Wed Aug 25 10:41:43 1999 PDT" -->
<!-- sent="Wed, 25 Aug 1999 19:23:58 +0200" -->
<!-- name="Oliver Rauch" -->
<!-- email="oliver.rauch@Wolfsburg.DE" -->
<!-- subject="Re: SANE V2" -->
<!-- id="" -->
<!-- inreplyto="SANE V2" -->
<title>sane-devel: Re: SANE V2</title>
<h1>Re: SANE V2</h1>
<b>Oliver Rauch</b> (<a href="mailto:oliver.rauch@Wolfsburg.DE"><i>oliver.rauch@Wolfsburg.DE</i></a>)<br>
<i>Wed, 25 Aug 1999 19:23:58 +0200</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#299">[ date ]</a><a href="index.html#299">[ thread ]</a><a href="subject.html#299">[ subject ]</a><a href="author.html#299">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0300.html">Oliver Rauch: "Re: SANE V2"</a>
<li> <b>Previous message:</b> <a href="0298.html">Harald Finster: "Re: microtek X6 advance and TMA"</a>
<li> <b>Maybe in reply to:</b> <a href="0296.html">Nick Lamb: "SANE V2"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0300.html">Oliver Rauch: "Re: SANE V2"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Nick Lamb wrote:<br>
<p>
<i>&gt; Some time after SANE_FRAME_BLAH is established we discover that the</i><br>
<i>&gt; existing backends and frontends have co-incidentally implemented</i><br>
<i>&gt; the same wrong behaviour. We could then re-write all the software,</i><br>
<i>&gt; and require users to upgrade immediately, or we could just do this:</i><br>
<i>&gt;</i><br>
<i>&gt; SANE_FRAME_BROKEN_BLAH = old value of SANE_FRAME_BLAH</i><br>
<i>&gt; SANE_FRAME_BLAH = newly issued frame type number</i><br>
<i>&gt;</i><br>
<i>&gt; Which makes it possible to auto-detect broken frames from the old</i><br>
<i>&gt; broken backends in a new frontend, and correct for it (if possible)</i><br>
<i>&gt; or at least avoid nasty surprises.</i><br>
<i>&gt;</i><br>
<p>
Hi Nick,<br>
if we use identifiers that do not say anyting we of course can change<br>
the meaning of this identifier without any probelms.<br>
<p>
But I think the advantages of identifiers who say something about the<br>
thing they identify is much more better than numbers.<br>
<p>
The second thing is that if we use a string as identifier we do not have<br>
to change sane.h all the time when we add a new format.<br>
That can make much problems, here only one example:<br>
( We will not distribute all frontends and the backends together in the future,<br>
this is the reason why xsane is not included into the sane package. )<br>
You can not find out with precompiler test (#ifdef ...) if there is a member<br>
in the enum or not. So if you try to compile a frontend that tries to uses<br>
a new frame format (SANE_FRAME_NEW_XYZ) but that one is<br>
not defined in the enum you get much problems that are not easy to<br>
solve.<br>
<p>
Bye<br>
Oliver<br>
<p>
<pre>
--
EMAIL: <a href="mailto:Oliver.Rauch@Wolfsburg.DE">Oliver.Rauch@Wolfsburg.DE</a>
WWW: <a href="http://www.wolfsburg.de/~rauch">http://www.wolfsburg.de/~rauch</a>
<p>
<p>
<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="0300.html">Oliver Rauch: "Re: SANE V2"</a>
<li> <b>Previous message:</b> <a href="0298.html">Harald Finster: "Re: microtek X6 advance and TMA"</a>
<li> <b>Maybe in reply to:</b> <a href="0296.html">Nick Lamb: "SANE V2"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0300.html">Oliver Rauch: "Re: SANE V2"</a>
<!-- reply="end" -->
</ul>