Comment 6 for bug 541119

Any comments on the desirability of the dbSuppressMacroWarnings patch I posted for this bug back in December? I'd like to either commit the change (to 3.15) or drop it from my tree. When suppression is turned on it really only makes the warnings less scary; I guess it could have 2 levels so even the new (softer) warning message can be omitted if we think that would be better. The parser will still find any syntax errors in the expanded output, so it's not really dangerous at all.