From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9748 invoked by alias); 7 Feb 2005 09:01:17 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 9041 invoked from network); 7 Feb 2005 09:01:07 -0000 Received: from unknown (HELO crossys.com) (80.99.7.107) by sourceware.org with SMTP; 7 Feb 2005 09:01:07 -0000 Received: from Kereszt by crossys.com with local (Exim 4.32) id IBDYEY-0002P0-LT for pthreads-win32@sources.redhat.com; Fri, 04 Feb 2005 12:54:34 +0100 Date: Mon, 07 Feb 2005 09:01:00 -0000 From: Keresztfalvi Laszlo To: pthreads-win32 Subject: localtime_r Message-ID: <20050204115434.GE3172@cross> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.1i X-SW-Source: 2005/txt/msg00010.txt.bz2 Hello, I've found that localtime_r() is a macro in pthread-win32 simply referencing the localtime() function. According to the MSDN localtime() works just like the UNIX version.. each call overwrites the static struct tm storage. Is this really thread safe? Thanks, Laszlo PS: a simple call like this: localtime_r (&tt, &ttm); causes MinGW to log "warning: value computed is not used"