Subj : Re: non obsolete equivalent of xmsg?
To   : borland.public.cpp.borlandcpp
From : "Regis St-Gelais" <regis.st-gelais@NOSPAMlaubrass.com>
Date : Fri Nov 14 2003 09:36 am




"Gary Setter" <setterg@worldnet.att.net> a écrit dans le message de
news:3fb4e773$1@newsgroups.borland.com...
>
> "Regis St-Gelais" <regis.st-gelais@NOSPAMlaubrass.com> wrote in message
> news:3fb3dcd1$1@newsgroups.borland.com...
> > How to modify this code to do the same thing without the xmsg is
obsolete
> > warning?
> <snip>
> > Regis St-Gelais
>
> Hi Regis,
>
> Shouldn't you be asking what exception class the code throws?
>
> If you are trying to catch exceptions in your own code, you might just use
a
> string or your own class or use the standard template libraries
<exception>
> classes.
>

This is a last resort catch for unandled exceptions

// some code is actualy   retval = TAppUmt().Run();

Thanks
-- 
Regis

.