ps. I looked at some contrib thread support in DJGPP and I was not
able
to find any PTHREAD compatible library but I've found two ones:
jtlwp20s.zip and pdmlwp03.zip. The second one is based on the 1-st
one so both uses the same mechanism to task switching which is
done in the interrupt what creates some problems. Because neither
DOS nor DJGPP CRTL is reentrant safe to use such threads is
necessary
to encapsulate all CRTL/OS function calls in code which disable
task
switching and then enable it when function returns. For such big
projects like Harbour with possible 3-rd party libraries it's very
hard to pass such condition so it will be hard for us to use them.
I think your implementation is perfect for us, plus even if DJGPP
had something to offer here, it would still be DJGPP specific, and
we also have dos/watcom.
What we can still do is to minimize reliance on CRTL calls, just
to skip that layer of compiler/compiler setting specific abstraction
and stick to local functions, ANSI C functions (+ POSIX extensions)
and OS calls.
I wonder what are the CRTL calls we're still using, there couldn't
be too many. (fopen, fprintf for sure - and for fopen there is a
dreaded MSVC warning shown, with no warning-free + proper CRTL
replacement)
[ The downside of course is that we have to take the burden to
reimplement, test and maintain these functions locally. ]
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
