|
| From: | David Durham |
| Subject: | Re: Questions |
| Date: | Mon, 04 Feb 2002 13:15:45 -0600 |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011221 |
David Sugar wrote:
Older and poorer compilers have different problems. For example, if you define a class foo in a common header that uses STL, and have an instance of foo in test1.cpp and in test2.cpp, you may have template generated object code in both test1.o and test2.o even when it has been subroutined and is identical/duplicate function calls. Newer compilers and linkers throw away duplicate code like this. Then there was a time not all c++ compilers could compile STL...My mistake, I meant "ThreadLock" when I said RWLock :). That's why you can't find it....As for realpath, I think it would have to provide an implimentation if one is not provided. realpath is far too useful for enforcing path restricted access policies.
What is the significance of the name 'ThreadLock'... 'RWLock' seems to make much more sense... And there may even be a better term from a CS textbook.
| [Prev in Thread] | Current Thread | [Next in Thread] |