> 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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
