Pete Robbins wrote:
Hi Martin.
Using stdcxx is certainly on our list of things to investigate. There are 2
ways in which we can use a C++ standard library:
1) Internally withing our own implementation code
2) Exposed on user APIs
We currently use stl within our implementation and the use of stl
classes on
our interfaces is currently under discussion in the SCA C++ Specification
group.
Ed Slattery took a look at using stdcxx but I have to admit I have had
little time to follw this up.
I need to take a look at your project and see what the benefits are.
FWIW, one of the major benefits of using stdcxx in a portable
C++ project is to bridge the inevitable and typically subtle
differences between implementations of the C++ Standard Library
you are likely to run into while porting Tuscany from the
mainstream platforms to others. stdcxx has been ported to and
works out of the box on the majority of today's C++ compilers
and (server) operating systems (see the list of certified
platforms here:
http://incubator.apache.org/stdcxx/#platforms).
If portability of localized data is important to Tuscany, stdcxx
comes with its own set of locales to guarantee the same behavior
regardless of the NLS on the operating system (which also tends
to differ from one operating system to another).
In addition to being highly portable, stdcxx often performs better
than the native C++ Standard Library that comes with the compiler
(this is especially true for HP aCC and Sun C++ and also to some
extent for IBM XLC++).
If there are any specific issues that are of particular concern
to you I would be happy to discuss them with you.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
