This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: C++ and STL?
- From: Sergei Gavrikov <sergei dot gavrikov at gmail dot com>
- To: "Paul D. DeRocco" <pderocco at ix dot netcom dot com>
- Cc: eCos Discuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Fri, 23 Sep 2011 18:51:50 +0300 (EEST)
- Subject: RE: [ECOS] C++ and STL?
- References: <77EC56E3C2394976967DA7002C6DB6E5@PAULD>
On Wed, 21 Sep 2011, Paul D. DeRocco wrote:
> > On Wed, 21 Sep 2011, gmail wrote:
> > Is there a package for STL and eCos 3.0?
>
> The problem with what was once called STL (which has actually been part of
> the C++ language since 1998) is that it has no way to report out-of-memory
> errors other than by throwing bad_alloc. uSTL doesn't seem to be any
> different. But last I looked, eCos didn't support C++ exceptions, because
> the kernel didn't provide the helper functions needed to make them
> thread-safe. eCosCentric's version did, but that was something you could
> only use if you bought their package. Is this still the case? I haven't
> worked with eCos for about four years now, so I haven't been keeping track.
Hi Paul,
How the eCos uSTL port can live "without" C++ exceptions handling is
described in eCos documentation
Chapter 9. uSTL library overview -> eCos specific changes/enhancements
http://www.ecos.sourceware.org/docs-latest/ref/ustl-overview.html
Well, it can make you write exceptions-less code, but, it is not evil,
google for "Cleaner, more elegant, and harder to recognize" article.
Sergei
> --
>
> Ciao, Paul D. DeRocco
> Paul mailto:pderocco@ix.netcom.com
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss