You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by ji...@apache.org on 2004/04/29 11:24:53 UTC
[jira] Created: (AXISCPP-79) Using the Same Allocation Mechanism
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-79
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-79
Summary: Using the Same Allocation Mechanism
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Axis-C++
Versions:
future (enh)
Assignee:
Reporter: Samisa Abeysinghe
Created: Thu, 29 Apr 2004 2:24 AM
Updated: Thu, 29 Apr 2004 2:24 AM
Environment: All platforms
Description:
Wrappers built around Axis C++ for memory management would become simpler if the same allocation mechanism is used.
In the current code, strings are allocated/deallocated using malloc/free and other types use new/delete
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Closed: (AXISCPP-79) Using the Same Allocation Mechanism
Posted by ax...@ws.apache.org.
Message:
The following issue has been closed.
Resolver: John Hawkins
Date: Fri, 15 Oct 2004 3:10 AM
W are changing the whole way we do C and C++ support so clsoing this defect.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-79
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-79
Summary: Using the Same Allocation Mechanism
Type: Improvement
Status: Closed
Priority: Minor
Resolution: WON'T FIX
Project: Axis-C++
Versions:
future (enh)
Assignee:
Reporter: Samisa Abeysinghe
Created: Thu, 29 Apr 2004 2:24 AM
Updated: Fri, 15 Oct 2004 3:10 AM
Environment: All platforms
Description:
Wrappers built around Axis C++ for memory management would become simpler if the same allocation mechanism is used.
In the current code, strings are allocated/deallocated using malloc/free and other types use new/delete
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Resolved: (AXISCPP-79) Using the Same Allocation Mechanism
Posted by ax...@ws.apache.org.
Message:
The following issue has been resolved as WON'T FIX.
Resolver: Samisa Abeysinghe
Date: Mon, 16 Aug 2004 5:15 AM
In case of class objects cannot use malloc/free as this will not call the constructor/destructor.
In case of serializer/deserializer, using new/delete would have performance hits.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-79
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-79
Summary: Using the Same Allocation Mechanism
Type: Improvement
Status: Resolved
Priority: Minor
Resolution: WON'T FIX
Project: Axis-C++
Versions:
future (enh)
Assignee:
Reporter: Samisa Abeysinghe
Created: Thu, 29 Apr 2004 2:24 AM
Updated: Mon, 16 Aug 2004 5:15 AM
Environment: All platforms
Description:
Wrappers built around Axis C++ for memory management would become simpler if the same allocation mechanism is used.
In the current code, strings are allocated/deallocated using malloc/free and other types use new/delete
---------------------------------------------------------------------
JIRA INFORMATION:
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