kopia lustrzana https://gitlab.com/sane-project/website
78 wiersze
3.2 KiB
HTML
78 wiersze
3.2 KiB
HTML
|
<!-- received="Fri Feb 26 00:05:19 1999 PST" -->
|
|||
|
|
<!-- sent="Fri, 26 Feb 1999 08:48:08 +0100" -->
|
|||
|
|
<!-- name="Svend Daugaard Pedersen" -->
|
|||
|
|
<!-- email="sdp@vip.cybercity.dk" -->
|
|||
|
|
<!-- subject="Re: Porting SANE backends" -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="36D5D35E.990ADB1B@wolfsburg.de" -->
|
|||
|
|
<title>sane-devel: Re: Porting SANE backends</title>
|
|||
|
|
<h1>Re: Porting SANE backends</h1>
|
|||
|
|
<b>Svend Daugaard Pedersen</b> (<a href="mailto:sdp@vip.cybercity.dk"><i>sdp@vip.cybercity.dk</i></a>)<br>
|
|||
|
|
<i>Fri, 26 Feb 1999 08:48:08 +0100</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#185">[ date ]</a><a href="index.html#185">[ thread ]</a><a href="subject.html#185">[ subject ]</a><a href="author.html#185">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0186.html">Milon Firikis: "Re: Porting SANE backends"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0184.html">Warren Early: "Re: UMAX Astra 1200S lamp question"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
Oliver Rauch wrote<br>
|
|||
|
|
<p>
|
|||
|
|
<i>>Svend Daugaard Pedersen wrote:</i><br>
|
|||
|
|
<p>
|
|||
|
|
<i>>> - don't use 'alloca()'</i><br>
|
|||
|
|
<i>>> this routine is not an ANSI routine and it is difficult</i><br>
|
|||
|
|
<i>>> (in many cases impossible) to implement in a C system not</i><br>
|
|||
|
|
<i>>> having it.</i><br>
|
|||
|
|
<i>>></i><br>
|
|||
|
|
<p>
|
|||
|
|
<i>>Thats no problem, changed it in the umax backend.</i><br>
|
|||
|
|
<p>
|
|||
|
|
The 'alloca()' is not the biggest problem (it is possible for me<br>
|
|||
|
|
to implement it). But it is not an ANSI C routine.<br>
|
|||
|
|
<p>
|
|||
|
|
<i>>> - don't use 'fork()' and related routines</i><br>
|
|||
|
|
<i>>> if you feel it is necessary, do it in a way that makes it</i><br>
|
|||
|
|
<i>>> easy to change the code (snapscan.c is a good example) or</i><br>
|
|||
|
|
<i>>> better: make this part of the code conditional.</i><br>
|
|||
|
|
<i>>></i><br>
|
|||
|
|
<p>
|
|||
|
|
<i>>What is the problem with fork. The amiga has a multi-tasking system,</i><br>
|
|||
|
|
<i>>so I don`t understand the problem.</i><br>
|
|||
|
|
<p>
|
|||
|
|
It's correct that amiga has a multi-tasking system (and the access<br>
|
|||
|
|
to the SCSI port is in fact always done in a separate task), but<br>
|
|||
|
|
'fork' is not an ANSI C routine and it is not easy to implement on<br>
|
|||
|
|
C systems not having it.<br>
|
|||
|
|
<p>
|
|||
|
|
The fact is that I have given up porting some of the backends because<br>
|
|||
|
|
of this 'fork'. As you can see from my comments, I know that there are<br>
|
|||
|
|
good reasons for using it. What I'm asking for is that it is used in<br>
|
|||
|
|
a way that makes it possible to remove (in the snapscan backend there<br>
|
|||
|
|
is code for the case that fork fails).<br>
|
|||
|
|
<p>
|
|||
|
|
<i>>Bye</i><br>
|
|||
|
|
<i>>Oliver</i><br>
|
|||
|
|
<p>
|
|||
|
|
Regards<br>
|
|||
|
|
Svend<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="0186.html">Milon Firikis: "Re: Porting SANE backends"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0184.html">Warren Early: "Re: UMAX Astra 1200S lamp question"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|