[ http://issues.apache.org/jira/browse/AXISCPP-149?page=comments#action_12360296 ]
Adrian Dick commented on AXISCPP-149: ------------------------------------- In reference to the comment made by Nadir ( http://issues.apache.org/jira/browse/AXISCPP-149#action_12360280 ): I had intended to use 'const' throughout, but as you mention there is no reason to use "const" at all in this case. So, I think we should go in and remove all the offending occurances - I don't believe this will make any significate difference to the API and it's use. (If it does the test suite should pick it up quickly enough) > Memory cleaning of generated C++ array code > ------------------------------------------- > > Key: AXISCPP-149 > URL: http://issues.apache.org/jira/browse/AXISCPP-149 > Project: Axis-C++ > Type: Improvement > Components: WSDL processing - RPC > Versions: 1.3 Final > Environment: All Platforms > Reporter: Samisa Abeysinghe > Assignee: Dushshantha Chandradasa > Fix For: 1.6 Alpha > > In case of Arrays, I noticed that the WSDL2WS tool is generating a > struct. > e.g. > typedef struct SOAPStruct_ArrayTag > { > SOAPStruct* m_Array; > int m_Size; > } SOAPStruct_Array; > The trouble here is that in case of returned values/parameters the user > has to delete the m_Array mamber explicitly. > I think a more cleaner way would be to use a class here and use a > destructor to clean memory. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
