Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
In-Reply-To: <Pine.LNX.4.55.0408092050550.3585@home.oyster.ru>
References: <Pine.LNX.4.55.0408092050550.3585@home.oyster.ru>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <776EA5E4-EA28-11D8-909C-000A958653C2@nxscientific.com>
Content-Transfer-Encoding: 7bit
Cc: dev@apr.apache.org
From: C K Tan <cktan@nxscientific.com>
Subject: Re: 1.0
Date: Tue, 10 Aug 2004 01:20:53 +0800
To: malc <malc@pulsesoft.com>

Second that. The Win32 conditional problem was not new. I reported it 
and submited a patch back on Oct 28, 2003. Someone was looking at it 
(forgot the name), but never did check in a fix... Along the way, 
someone else ran into it and filed a report in bugzilla (id# 27654). 
Still no fix. I have given up waiting. For consolation, there isn't any 
deadlocks if I use only the broadcast() primitive.

-cktan


On Aug 10, 2004, at 12:57 AM, malc wrote:

> Hi,
>
> Perhaps im way off on this and please do correct me if i am wrong.
>
> Condition variables on Win32 are broken, if you are going to label
> APR with 1.0 mark and release it right now, without mentioning this
> fact in big red letters, this would essentially be equal to releasing
> a trojan horse - a free, attractive, portable thing with a stamp of
> greatness (Apache) in its name, but deadly.
>
> Not only code responsible for condvars under Win32 lacks any error
> checking whatsoever, there are also races, stuff which (to the best
> of my knowlege) results in upredictable behavior, so people using
> it will be bitten.. hard.
>
> -- 
> mailto:malc@pulsesoft.com