DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20642>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20642 Lack of ctor definitions in XMemory prevents build on VC++ 7.0 with WPO enabled ------- Additional Comments From [EMAIL PROTECTED] 2003-06-10 18:19 ------- I don't think you understood what I was saying, so I will repeat it. It is a very common idiom in C++ to declare the copy constructor and the assignment operator as private and to provide no definition for them, if copy and assigment semantics make no sense for a class. There is nothing wrong with doing this, and there is nothing in the C++ standard which forbids it. In fact, it works on all compilers I know of. I was simply responding to your report, which blamed the problem on a special optimization option in MSVC 7.0, and requested a change in the source code. If this really were a problem with classes that make use of this idiom, that would be a big problem, and would indicate a bug in the Microsoft compiler. When I said "huge amounts of code," I was not speaking only of the Xerces code base, but rather all of the code that has been written everywhere using this idiom. Remember, you are the one who stated the error was because those member functions were declared but not defined. I was simply responding to your assertion. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
