🚀 go-pugleaf

nevermind, I figured it out - had to remove the open and close parenthesis -
this leads to the next question:

I have several macros defined - some use the parenthesis and some don't -
when are these required and when not?  Or maybe they're not required at
all???  Here's an example of where I use them, and below is an example of
when I shouldn't (I've removed the parenthesis that caused the original
message to have a problem).

#define AMF_REPORT_WARNING(message) ( \
            AMF_AF_ErrorHandlerThreadC::NotifyUser ( \
            AMF_AF_ExceptionC (AMF_AF_ExceptionC::ET_WARNING,             \
            message, __FILE__,,, __FUNC__, __LINE__)) )

Thanks again for the help!!

"p Anders" <paul.anderson@jhuapl.edu> wrote in message
news:4062cd03$1@newsgroups.borland.com...
> I'm trying to write a macro to use in place of a catch clause in order to
> save myself 18 lines of code wherever I need the catch clause.  The macro
is
> defined as:
>
> #define AMF_BaseC_CATCH_EXCEPTION(Severity)
>                                     \
>    catch (AMF_AF_ExceptionC& amfException)
> \
>
>
{                                                                          \
>       amfException.SetType(Severity);
> \
>       sm_ErrorHandler->ReportException(amfException);
> \
>       }
> \
>    catch (runtime_error& e)
> \
>
>
{                                                                          \
>       AMF_AF_ExceptionC amfException(e);
> \
>       amfException.SetType(Severity);
> \
>       sm_ErrorHandler->ReportException(amfException);
> \
>       }
> \
>    catch (...)
> \
>
>
{                                                                          \
>       AMF_AF_ExceptionC amfException(Severity,
> \
>                                      "Caught an unspecified
> AMF_AF_ExceptionC!", \
>                                      __FILE__, m_tClassName.c_str(),
> __FUNC__);  \
>       sm_ErrorHandler->ReportException(amfException);
> \
>       }
>
> I get a compoile error that says a "catch clause" was expected.
>
> Can I not use a macro here?
>
> Thanks.
>
>