Hi All, I removed the use of STL from the external API of the exception model. Instead of std::string, I used char* to store exception message string. I used std::string only within the class as local variables. So it does not course any problem. I tested this and committed to the cvs.
My thank goes to Mark, Samisa and Henrik for their thoughts and help on fixing this issue. Regards, Dushshantha -----Original Message----- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Sunday, July 17, 2005 10:55 PM To: Apache AXIS C Developers List Subject: Re: Fw: Using STL (Was: Exception model (more thoughts)) > Does anyone have links to the threads? Here is one which includes few more within it: http://marc.theaimsgroup.com/?l=axis-c-dev&m=109706643622174&w=2 Thanks, Samisa... On 7/17/05, Mark Whitlock <[EMAIL PROTECTED]> wrote: > > > > > Hi Henrik, > Having STL on the external Axis C++ API means that users have to build > their applications with the same compiler that was used to build Axis C++, > or else rebuild Axis C++ themselves. This is because different compilers > have different implementations of the STL. > I remember we have had lengthy discussions in the past about STL on this > mailing list. Does anyone have links to the threads? > Mark > Mark Whitlock > IBM > > ----- Forwarded by Mark Whitlock/UK/IBM on 16/07/2005 21:57 ----- > > "Henrik Nordberg" > <henrik.nordberg@ > edgewaystech.com> To > "Apache AXIS C Developers List" > 15/07/2005 18:10 <[email protected]> > cc > > Please respond to Subject > "Apache AXIS C Re: Using STL (Was: Exception model > Developers List" (more thoughts)) > > > > > > > > > > > I think it is worth taking a closer look at this issue, because using the > STL (standard C++, really) can make the code less buggy (because you worry > less about pointers), easier to understand (for C++ programmers) and more > compatible with existing C++ code. > > What platforms have problems and what are those problems? > How does using STL only within get around those problems (the code still > needs to be compiled)? > > I don't mean to cause trouble, I truly want to understand this problem. C++ > > has come a long way and I think Axis-C++ can benefit from that. > > Thanks > - Henrik > > ----- Original Message ----- > From: "Samisa Abeysinghe" <[EMAIL PROTECTED]> > To: "Apache AXIS C Developers List" <[email protected]> > Sent: Friday, July 15, 2005 9:14 AM > Subject: Re: FW: Exception model (more thoughts) > > > As far as I know, some platorms have problems with STL, hence we use > STL only within. > > Samisa... > > On 7/12/05, Henrik Nordberg <[EMAIL PROTECTED]> wrote: > > What are those "incompatibilities in the STL."? > > > > Thanks > > - Henrik > > > > On 7/4/05, Mark Whitlock <[EMAIL PROTECTED]> wrote: > > > Hi Dushshantha, > > > STL is being removed from the Axis C++ external API (AXISCPP-681 and > > > others). If you are OK with this, please could you make m_sMessage a > > const > > > char* instead of a std::string? I realise this involves more code but > > it > > > helps to avoid incompatibilities in the STL. > > > Thanks, > > > Mark > > > Mark Whitlock > > > IBM > > > > > > >
