[
https://issues.apache.org/jira/browse/XERCESC-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Massari resolved XERCESC-1380.
--------------------------------------
Resolution: Fixed
Fix Version/s: 3.1.0
Assignee: Alberto Massari
The autoconf test is in SVN
> Unneccessary definition of extra delete operator causes compiler error
> ----------------------------------------------------------------------
>
> Key: XERCESC-1380
> URL: https://issues.apache.org/jira/browse/XERCESC-1380
> Project: Xerces-C++
> Issue Type: Bug
> Affects Versions: 2.6.0
> Environment: Solaris 2.8 with compiler SPARCompiler 4.2
> Reporter: Maciek Samsel
> Assignee: Alberto Massari
> Fix For: 3.1.0
>
>
> So anyway why do you need to define that extra delete operator?:
> //The Borland compiler is complaining about duplicate overloading of
> delete
> #if !defined(XML_BORLAND)
> /**
> * This method provides a matching delete for the placement new
> *
> * @param p The pointer to the allocated memory
> * @param memMgr An application's memory manager
> */
> void operator delete(void* p, MemoryManager* memMgr);
> #endif
> SPARCompiler 4.2 (as probably a few others) does not recognize that operator
> as valid and report an error.
> Please make appropriate macro declarations (not only for Borland as it is
> now) in platform specific files as well as conditional generation check in
> files:
> xerces-c-src_2_6_0/src/xercesc/util/XMemory.hpp
> xerces-c-src_2_6_0/src/xercesc/util/XMemory.cpp
> The check could be as follows:
> #if !defined(XML_BORLAND) && !defined(NO_DELETE_OVERLOAD)
> ...
> #endif
> FYI, the code compiles just fine without operator.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
