Re: [dev] warnings01: Windows no copy possible warnings

2005-10-05 Thread Stephan Bergmann
Nikolai Pretzell wrote: Stephan Bergmann wrote: Nikolai Pretzell wrote: [...] Conclusion and suggestion = 1) The warnings don't give any additional information. Any attempt to copy such a class results in a compiler error anyway. The information is given when

[dev] warnings01: Windows no copy possible warnings

2005-10-04 Thread Nikolai Pretzell
Hi, warnings under Windows there exist the following four warnings: C4625: copy constructor could not be generated because a base class copy constructor is inaccessible C4626: assignment operator could not be generated because a base class assignment operator is inaccessible C4511:

Re: [dev] warnings01: Windows no copy possible warnings

2005-10-04 Thread Nikolai Pretzell
Nikolai Pretzell wrote: workaround when keeping the warnings The warnings can be work-arounded by declaring copy-constructor and assignment-operator explicitely private in every derived or containing class like this: class C : public Bcd {public:

Re: [dev] warnings01: Windows no copy possible warnings

2005-10-04 Thread Thorsten Behrens
Nikolai Pretzell [EMAIL PROTECTED] writes: [about another one of those MSVCC 'hey, you've just used a C++ language feature' warnings] So, my suggestion: let's switch off the windows warnings C4625, C4626, C4511, C4512. +1 -- Thorsten If you're not failing some of the time, you're not

Re: [dev] warnings01: Windows no copy possible warnings

2005-10-04 Thread Stephan Bergmann
Nikolai Pretzell wrote: [...] Conclusion and suggestion = 1) The warnings don't give any additional information. Any attempt to copy such a class results in a compiler error anyway. The information is given when defining the class, not when using it, so the warning