Don Cragun <dcragun at sonic.net> wrote:
> The one-pager for this project says (in section 3.6) that it doesn't
> duplicate core Solaris components. But the description of the Pth
> library provided by this case sure sounds like it is trying to duplicate
> the behavior of the Solaris pthread library and major chunks of basic
> libc functions like read[v] and write[v].
>
> Why shouldn't this be considered a duplication of the core Solaris POSIX
> threads features even though it adds a "pth_" to the front of a bunch of
> standard function names?
It depends on the intention for this "duplication".
I am not sure if you did try to write portable software before.
In many cases, you may implement replacements for POSIX, so reimplementation of
POSIX functions only appear on platforms that are not POSIX compliant.
In case of threads, you would need to write something as big as Cygwin if you
like to use threads in an application that is also portable to Win-NT.
If you like to implement a smaller solution, you end up with something that may
only be close to the official POSIX thread interface if you like to support
Win-NT. This is mainly a result of the ideosyncratic mutex implementation
from Microsoft.
If the intention of this "duplication" is portability, it is OK for me.
J?rg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
joerg.schilling at fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
