In general it should not be too hard to search source files for "{$" or "(*$" and edit directives.
That does not help.
The original problem was to support specifying parameters as unused in a way that is source code compatible between MW and GPC. As I sated, I can specify a parameter as being unused in GPC using "attribute ( unused);" and use a define that expands to "attribute ( unused );" in GPC and nothing in MW. But I can only do this in MW by using {$unused(paramname)} which I cannot "hide" from GPC since I can't use a macro to expand to a pragma.
I don't mind (indeed am clearly perfectly willing) changing the source code to whatever is required to make it source code compatible, but currently there is no mechanism to suppress the warning that is source code compatible between the two.
At 7:53 -0400 20/9/04, CBFalconer wrote:
My attitude in PascalP was to ignore all unrecognized directives, and to spit out a warning for any such. After all, they are comments.
Since the initial comment is to suppress a warning, adding a warning to complain about the attempt to suppress a warning would sort of defeat the purpose! Peter. -- http://www.stairways.com/ http://download.stairways.com/