Hi,
On Wed, Oct 08, 2003, Henning Meier-Geinitz wrote:
system-function will then be done in sanei_thread_begin.=20
-- int sanei_thread_begin( int(callback)(void*args), void *args)
Yes, that's ok I think. I've already thought about that because there
is no way to return a status with the
On Thu, 9 Oct 2003 08:40:11 +0200, Gerhard Jaeger wrote:
...
By using this sanei_thread stuff, I think the os2_readerprocess is also
obsolete, but this has to be checked by whoever...
...
Franz, I think you can to some investigation on OS/2.
Are you able to make the test-backend work there?
I
Hi,
On Dienstag, 7. Oktober 2003 13:29, Henning Meier-Geinitz wrote:
The limitation is that only one parameter can be used for the
forked/threaded process?
Yeap, that's life ;-)
No, I mean this is no real problem
Currently I see two things that has to be solved:
1.) the interface to
Hi,
On Wed, Oct 08, 2003 at 08:56:29AM +0200, Gerhard Jaeger wrote:
1.) I'd like to change the interface of the function to be called in the
forked process to: int func_to_call( void*). The adaption to the different
system-function will then be done in sanei_thread_begin.
-- int
Hi,
On Sun, Oct 05, 2003 at 06:16:12PM +0200, Jaeger, Gerhard wrote:
I've currently added pthread support to the sanei_thread lib and changed
the Plustek backend, so that it will use threading instead of forking on
MacOS X. Could somebody please test this?
Also the detection of pthreads is
On Sonntag, 5. Oktober 2003 23:54, Henning Meier-Geinitz wrote:
Hi,
On Sun, Oct 05, 2003 at 06:16:12PM +0200, Jaeger, Gerhard wrote:
I've currently added pthread support to the sanei_thread lib and chan=
ged
the Plustek backend, so that it will use threading instead of forking=
on
MacOS
