Re: (Some) C++ support?

Thus spake Paul Sokolovsky ([email protected]):
> > And if you have a program that does not use STL, dietlibc still needs
> > to supply some functions for parsing ELF debug symbols because that's
> > how C++ exception handling works on Linux.  The compiler generates
> > code using those functions, and we don't have them.
> Exceptions?! No, supporting those in dietlibc didn't even come to my
> mind.

Uh, if you use any kind of STL, you need exception support.
All the containers in the STL can throw.
Also, operator new throws.

> Before even using them, there should be decent implementation of
> them in mainstream compilers, not typical setjmp/longjmp crap how it
> was few years ago, so now everyone just dreads to use them. Exceptions
> and RTTI of course have their uses too, but I don't remember seeing not
> too big C++ app lately which wouldn't use -fno-exceptions -fno-rtti.

Exceptions have not been using setjmp/longjmp for 10+ years on Linux, I
would say around 15 years even.

Which is exactly the problem now for us, because setjmp/longjmp we
support in dietlibc :-)

Felix