Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:2968
Return-Path: <sascha@schumann.cx>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 17398 invoked from network); 29 Jun 2003 14:15:24 -0000
Received: from unknown (HELO milton.schell.de) (217.160.72.35)
  by pb1.pair.com with SMTP; 29 Jun 2003 14:15:24 -0000
Received: (qmail 5424 invoked by uid 501); 29 Jun 2003 14:15:23 -0000
Received: from unknown (HELO eco.foo) (80.143.52.250)
  by kdserv.de with SMTP; 29 Jun 2003 14:15:23 -0000
Received: from localhost (localhost [127.0.0.1])
	by eco.foo (Postfix) with ESMTP id 67D79300C6
	for <internals@lists.php.net>; Sun, 29 Jun 2003 16:15:23 +0200 (CEST)
Date: Sun, 29 Jun 2003 16:15:23 +0200 (CEST)
X-X-Sender: sas@eco.foo
To: internals@lists.php.net
Message-ID: <Pine.LNX.4.53.0306291615110.28363@eco.foo>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] Apache 2 support (fwd)
From: sascha@schumann.cx (Sascha Schumann)

> I agree but I meant different thing.

    From my POV, it is up the author(s) of a specific piece of
    software to declare their code thread-safe.  Such info can
    then be tracked in a central document.  One can augment such
    a process by providing audit guidelines on how to approach
    the topic.

    Regarding automating the process - feel free and try to
    implement one.  The major hurdle is the filter lists you need
    to define for every possible C run-time environment /
    compiler combination, because each of those defines globals
    themselves.

    Here is an example output of nm for a dummy programm with two
    globals.  All symbols marked with [bBdD] are globals.

    http://tellyd2.de/nm.txt

    - Sascha