axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lah...@opensource.lk
Subject RE: STL elimination - Suggestions
Date Mon, 09 Aug 2004 13:09:09 GMT
Hi All,

Very few of the current api header files has methods which has stl string
as its arguments and return types. It is good if we could eliminate them.
Then even if Axis C++ engine internally use stl it does not expose stl to
its users.But this change may lead corresponding changes to the wsdl2ws
tool.
In tool generated files also in AxisClientException class there are some
stl string 's are used.

Lahiru Wimalasiri




> Hi All,
>
>    There are some STL string used in AxisClientException which is
> generated by the tool. To eliminate these which are expose to client is
> it necessary to remove stl string from API's expose to client.
>
> Lahiru Wimalasiri
>
>
>
>
>
>> Hi Lahiru,
>>     What are the WSDL files that you used to check this?
>> Thanks,
>> Samisa...
>>
>> --- lahiru@opensource.lk wrote:
>>
>>> Hi All,
>>>
>>> I have checked the generated code and already there are no any stl
>>> expose
>>> to the client.
>>>
>>> Lahiru Wimalasiri
>>>
>>> > Hi all,
>>> >        I have fixed the memory leaks in the string class and tested
>>> with
>>> > the code. It works fine with the code and need to be further
>>> > testing. I suggest eliminate stl so that it is not exposed to
>>> > client although it is used inside the engine. There are several
>>> > advantages by doing this.
>>> >
>>> > 1) Ability to support C. Other wise we need extra wrappers.
>>> > 2) Some times users may face portability challenges if STL is
>>> exposed.
>>> > 3) It is easier to manipulate an STL string, but char* is the
>>> standard
>>> > string format in C/C++. so giving char* instead of STL string, gives
>>> the
>>> > user more flexibility.
>>> >
>>> > Lahiru Wimalasiri
>>> >
>>> >
>>> >
>>> >> Hi Lahiru,
>>> >>
>>> >> I had a look at the code and did some testing. Found that it has the
>>> >> required functionality of stl::string that's great!.
>>> >>
>>> >> Kenneth Chiu has already pointed out the problems and improvements
>>> to
>>> be
>>> >> done.
>>> >>
>>> >> I used purify and found the memory leaks. I have attached the Purify
>>> >> output file that shows the memory leaks. I hope this helps
>>> >>
>>> >> ---
>>> >> Susantha
>>> >>
>>> >>> -----Original Message-----
>>> >>> From: lahiru@opensource.lk [mailto:lahiru@opensource.lk]
>>> >>> Sent: Thursday, June 03, 2004 4:59 PM
>>> >>> To: Apache AXIS C Developers List
>>> >>> Subject: RE: STL elimination - Suggestions
>>> >>>
>>> >>> hi all,
>>> >>>
>>> >>>  Please have a look at the Astring class implemented below and
>>> provide
>>> >>> your comments. The  files are attached with this mail.
>>> >>>
>>> >>> rgds,
>>> >>> Lahiru
>>> >>>
>>> >>> > At 10:13 AM 5/6/2004 +0530, you wrote:
>>> >>> >>What I would suggest -
>>> >>> >>1. expose a small set of classes and make the interface
stl-free
>>> >>> >>2. in your internal classes you can still use stl
>>> >>> >>
>>> >>> >>Why do you want to remove stl all-together?
>>> >>> >>
>>> >>> >> > -----Original Message-----
>>> >>> >> > From: Kenneth Chiu [mailto:chiuk@cs.indiana.edu]
>>> >>> >> > Sent: Thursday, May 06, 2004 9:41 AM
>>> >>> >> > To: Apache AXIS C Developers List
>>> >>> >
>>> >>
>>> >
>>> >
>>> >
>>>
>>>
>>
>>
>>
>>
>> __________________________________
>> Do you Yahoo!?
>> New and Improved Yahoo! Mail - Send 10MB messages!
>> http://promotions.yahoo.com/new_mail
>>
>>
>
>
>


Mime
View raw message