Re: Using STL (Was: Exception model (more thoughts))

[Henrik Nordberg <he...@edgewaystech.com>]

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" <sa...@gmail.com>
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
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 <he...@edgewaystech.com> wrote:
> What are those "incompatibilities in the STL."?
>
> Thanks
>  - Henrik
>
> On 7/4/05, Mark Whitlock <ma...@uk.ibm.com> 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
>
>