Thanks. Right, I've seen that C #pragma thing. That's exactly what I'm talking about. I'll take a look at it again.
It is our own messages I'm talking about, not the invoked compilers, and as you imply, it's probably most relevant to warning messages, because things like "can't open input dataset" are hard to ignore. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ray Mullins Sent: Friday, March 10, 2006 7:08 AM To: [email protected] Subject: Re: Any products that let you ignore certain messages? Sí, yo comprendo, creo que si. Ass/u/me/ing you're just looking for precedent, and for messages your product issues... Many C/C++ compilers have a #pragma option (varies from compiler to compiler, of course) that can suppress (and then unsuppress) messages. I have had to use it before to suppress silly M$ VC messages. (Thank you very much, M$, I do know what I'm doing, as opposed to some of your programmers.) But if it's the compilers being called from your product...that's tougher. Maybe something in the listing exits, but that would require the ability to change compiler behavior from inside the exit. Besides, in the case of E or S level compiler errors, the compiler may not generate code anyway, so even if you suppressed one E level message, the object deck may be worthless or even not exist, then the binder will barf (technical term) on the empty input. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
