Re: Question about static class objects

Yes, that code will very likely have problems in a multi-threaded program. It will be OK iff you can ensure that just a single thread at a time calls Zap::list(). For multi-threaded operation the accessor function is a rather poor design, and one would normally derive a class from TList that applies a mutex to the appropriate class functions....

I have no need or desire for multiple threads. Note that writing a program to be thread safe involves overheads, and can be rather complicated, so one does it only when necessary.

Tom Roberts

Konstantin Olchanski wrote:
> On Tue, May 27, 2008 at 12:01:57PM -0500, Philippe Canal wrote:

>> TList &Zap::list() {
>>    static TList list;
>>    return list;
>> } 
>> which anyway is slightly better in term of C++ style :)