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 copy ctor definition in XMemory prevents build on VC++ 7.0 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Summary|Lack of ctor definitions in |Lack of copy ctor definition |XMemory prevents build on |in XMemory prevents build on |VC++ 7.0 with WPO enabled |VC++ 7.0 ------- Additional Comments From [EMAIL PROTECTED] 2003-06-11 12:03 ------- David, thanks for your reply! You are indeed right. In fact, I've quite often used the very same thing in my own code, so I don't know what I was thinking of. Sorry! Neil, I grabbed the CVS source, and I can now confirm that the changes to XMemory does the trick. However, it wasn't the move from private to protected that made it work, but rather that the copy constructor now has a definition (like I suggested). This is what it looks like now in XMemory.hpp: XMemory(const XMemory&) { } Thanks for looking into this! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
