You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by bu...@apache.org on 2003/06/11 14:04:00 UTC
DO NOT REPLY [Bug 20642] -
Lack of copy ctor definition in XMemory prevents build on VC++ 7.0
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
carbe771@student.liu.se 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 carbe771@student.liu.se 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: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org