"Garrett D'Amore" <gdamore at sun.com> wrote:
> One more point... GNU Pth specifically states that it only executes on a
> single CPU at a time, and that there are some restrictions on what
> applications must assume that make it easier to write such
> applications. (For example, they need to be MT safe, but not re-entrant.)
>
> Rewriting GNU Pth to use native threads might sound like a great idea,
> but it might have unforeseen side effects for applications.
Note that the applications that use Pth may even not be MT safe.
- They may not use the MT errno
- They may use non-atomic "instructions" to synchronize "threads"
and fail in case of real concurency.
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
