When using destructors, Bison 2.4 currently warns you of any destructable symbol values that are not mentioned in an action, on the theory that if you want them finalized in case of errors, you surely must want them finalized in the normal case as well. Unfortunately, I have an application where this is not true (never mind why), so I am stuck with enormous numbers of bogus warnings. The -Wnone option, contrary to the documentation, does NOT suppress all categories of warnings---in particular, not these. Perhaps its reach should be extended, or there should be a category of destructor whose action really is intended by the programmer to be needed ONLY in case of error (so that it does not cause warnings)?
Paul Hilfinger
