Re: [Dev-C++] about exceptions

[Lists <li...@dr...>]

As I see it, if you have a bottom level function throwing an exception, and
a top level function catching it, but to identify the mid-level function it
travelled through.. you would need to have to rethrow it in the midlevel
function with a minor tweak to identify itself.  I don't think there's any
way around that.

Tvienti

----- Original Message -----
From: "Zodiaq" <zo...@ac...>
To: <Dev...@li...>
Sent: Thursday, May 15, 2003 7:03 PM
Subject: [Dev-C++] about exceptions


> Hello all Dev-cpp-users,
>
>   I have one important question - this small example will show what my
> mail is all about... let's say I have one major function (FunQ) which
> calls many smaller functions(fun1 - fun20), and all of these functions
> uses the same small function (smallFun) which conditionaly may throw
> exceptions... only FunQ catches these exceptions... is there some a
> way to know which way this exception came apart from rethrowing it
> from funX (where X is number 1-20)... adding in many points in every
> fun1-fun20 try...catch is what I want to avoid... maybe there is
> something similar like __LINE__ or __FILE__ but about call stack??
>
> --
> regards Zodiaq
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>
>