Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 46534 invoked by uid 500); 26 Dec 2002 01:41:45 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 46361 invoked from network); 26 Dec 2002 01:41:43 -0000 Message-Id: <5.1.0.14.2.20021225194013.02c48fb0@pop3.rowe-clan.net> X-Sender: admin%rowe-clan.net@pop3.rowe-clan.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 25 Dec 2002 19:41:23 -0600 To: INOUE Seiichiro From: "William A. Rowe, Jr." Subject: Re: [Resend] Re: apr_os_thread_get() weirdness on Win32 Cc: dev@apr.apache.org In-Reply-To: <20021225.013347.59678232.inoue@ariel-networks.com> References: <20020906.045433.71081822.inoue@ariel-networks.com> <20020906.045433.71081822.inoue@ariel-networks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 26 Dec 2002 01:41:47.0151 (UTC) FILETIME=[F3D609F0:01C2AC7F] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N At 10:33 AM 12/24/2002, INOUE Seiichiro wrote: >This is an old story. >I would like to make it clear. > >When we need the Win32 thread handle from libapr, the following code is a proper code? > >HANDLE h; >apr_thread_t *thd; >apr_os_thread_get((apr_os_thread_t**)&h, thd); Hes, it should be. And the cast should be unnecessary ... if it is, we have a bug. On win32, apr_thread_t should be a HANDLE already. Bill