[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-tech
Subject:    Re: BSD auth question, auth_call() fails - flame warning
From:       Cédric_Berger <cedric () berger ! to>
Date:       2008-01-31 11:29:31
Message-ID: 47A1B11B.5030100 () berger ! to
[Download RAW message or body]

> Compile without optimization, once with -lpthread and once without. The binary
> linked against libpthread will die in auth_call.

<beginRant>
I've worked programming with unix and win32 a lot, and I find
it far more enjoyable to work with unix APIs, which are as a
general rule far better designed.

There is one area though that MS got right since the first NT
release: thread support:
    One simple 1:1 thread safe library, period.

It's unbelievable to me that almost 20 years later the unix
land is still dealing with an orgy of incompatible, buggy,
user-selectable 1:N, N:1, N:M, xxxx

How about following M$ for once and providing ONE simple 1:1
thread safe library, libc, and kill all those -lthread,
-lpthread, libc_r and similar mess?

Or is that just the NIH syndrome again?
<endRant>

[prev in list] [next in list] [prev in thread] [next in thread]