Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of alin.harmony@gmail.com
 designates 64.233.184.226 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=OFVsUGlPz5E6Rdpp+m4Pdkvvz1WkVyTUcDJN1RLqfWtzyY2Cyj2ttlZhn3HrZ6Govw5o6zCUvpXPul1dFLqU4Ec0cSR2DUruHmmJc9ciFk3g8yA+5grVdllHLP0OTD/l7kdRqxK7ibT4XZAa9P4ArNCMx3H+klwfiKP9Zn1eIj0=
Message-ID: <3ae04f990706211035x156845d7l78cc874f4469bb8b@mail.gmail.com>
Date: Thu, 21 Jun 2007 13:35:20 -0400
From: "Angela Lin" <alin.harmony@gmail.com>
To: dev@harmony.apache.org
Subject: hythread_detach limitation
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi folks,

Could you take a peek at:
https://issues.apache.org/jira/browse/HARMONY-4237

Text:
The docs/comments for hythread_detach() and
HyThreadLibrary->thread_detach() should be amended to note the
limitation that these functions can only be used to detach the
_current_ thread (and not any arbitrary thread).

Because these funcs accept a hythread_t parameter, this may not be obvious.

This limitation exists because the implementation may use some thread
local storage.


It's not quite a bug. I think it's a limitation that was accidentally
omitted from our original document/spec for the hythread API.

I hope you think this limitation is reasonable - it's
implementation-influenced, but I think other implementations might
want to use thread local storage too.

-- 
Angela Lin, IBM Ottawa Software Lab