[ http://issues.apache.org/jira/browse/XERCESC-1058?page=history ]
Alberto Massari resolved XERCESC-1058:
--------------------------------------
Assign To: (was: Xerces-C Developers Mailing List)
Resolution: Won't Fix
The warning means that the object being thrown cannot be caught using
catch(Type), but has to be caught by a catch(Type&).
The behavior is by design, as XMemory has a protected copy constructor.
Alberto
> XMemory related warning
> -----------------------
>
> Key: XERCESC-1058
> URL: http://issues.apache.org/jira/browse/XERCESC-1058
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: Nightly build (please specify the date)
> Environment: Operating System: Windows NT/2K
> Platform: PC
> Reporter: Martin Krumpolec
>
> When building (VS.NET 2003) my app with latest CVS snapshot (20031120171656)
> I
> keep getting warning (level 4) :
> D:\Utils\xerces\src\xercesc\internal\XSerializeEngine.hpp(664) : warning
> C4673:
> throwing 'xercesc_2_4::XSerializationException' the following types will not
> be
> considered at the catch site
> D:\Utils\xerces\src\xercesc\internal\XSerializeEngine.hpp(664) : warning
> C4671: 'XMemory' : the copy constructor is inaccessible
> I'm not sure if it is really safe to ignore this warning ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
