Mail Archives: djgpp/1999/08/20/10:43:22
Works OK for me. I specially tested not only with installation I'm
normally using but special one for tests ( gcc295b.zip, gpp295b.zip,
lgpp295b.zip, bnu281b.zip, djdev202.zip, djtzn202.zip only, no changes
after unzipping)
Do You actually have djdev202.zip installed? There were special
workaround in port of gcc-2.8.1 which enabled use of exceptions
with v2.01. This workaround is dropped in ports of egcs-1.1.2 and
gcc-2.95.
It's also mentioned in readme.djgpp that djdev202 or above is required.
Andris
On 20 Aug 99, at 12:42, Rob Kramer wrote:
> Hi there,
>
> A strange problem with g++ exceptions here.. Take the following simplified
> example:
>
> ------------------------------
> #include <iostream>
>
> class testException
> {
> public:
> };
>
>
> void main()
> {
> cout << "test " << endl;
>
> try {
> throw testException();
> } catch (testException &e) {
> cout << "caught testException.." << endl;
> } catch (...) {
> cout << "or anything.." << endl;
> }
> }
>
> This works fine on gcc 2.8.1, but aborts on 2.95. (I had similar troubles with
> egcs 1.1.x, so never made the switch to that compiler).
>
>
> I upgraded from gcc 2.8.1 by installing bnu291, gcc295b and gpp295b in
> that order, and looked for old files according to readme.djgpp (they were
> gone already).
>
> It seems the throw is never caught, but surely exception handling can't be
> *that* broken? I wonder what I'm doing wrong this time :)
>
- Raw text -