[ 
http://issues.apache.org/jira/browse/XERCESC-1323?page=comments#action_57377 ]
     
Robert Buck commented on XERCESC-1323:
--------------------------------------

Bottom Line on Top:

Thrown objects MUST have both the destructors and copy constructor exposed; 
this includes superclasses as well.

Regarding the last comments in  the following issue:

http://issues.apache.org/jira/browse/XERCESC-1058

Alby, you are incorrect. This is implementation defined by specification. In 
many C++ runtime implementations, the object, whose class or superclasses lack 
a public constructor, cannot be caught by a catch-ref block either. Taking a 
look at the C++ Std, § 15.1, subsections 4-6, and § 15.4, subsection 18, it is 
very apparent that Xerces-C is ill-formed.

Please reopen the cited issue, and fix Xerces.



> CLONE -XMemory related warning
> ------------------------------
>
>          Key: XERCESC-1323
>          URL: http://issues.apache.org/jira/browse/XERCESC-1323
>      Project: Xerces-C++
>         Type: Bug
>   Components: Build
>     Versions: Nightly build (please specify the date)
>  Environment: Operating System: Windows NT/2K
> Platform: PC
>     Reporter: Robert Buck

>
> 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]

Reply via email to