warnings: define warning classes at point of usemkwarnings

It is extremely desirable to allow the user fine-grained control of
warnings, but this has been complicated by the fact that a warning
class has had to be defined in no less than three places (error.h,
error.c, nasmdoc.src) before it can be used in source code. Instead,
use a script to define these via magic comments at the point of use.

This hopefully will encourage creating new classes as needed.

Signed-off-by: H. Peter Anvin (Intel) <hpa@zytor.com>

1 files changed, 3 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index 82ec14ea..7afbbe25 100644
--- a/.gitignore
+++ b/.gitignore
@@ -48,6 +48,7 @@ TAGS
 /asm/pptok.ph
 /asm/tokens.h
 /asm/tokhash.c
+/asm/warnings.c
 /config/config.h
 /config/config.h.in
 /config.log
@@ -66,6 +67,8 @@ TAGS
 /doc/info
 /doc/inslist.src
 /doc/version.src
+/doc/warnings.src
+/include/warnings.h
 /macros/macros.c
 /misc/omfdump
 /nasm