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, 6 insertions, 0 deletions

diff --git a/asm/parser.c b/asm/parser.c
index 04def6b4..c34f8337 100644
--- a/asm/parser.c
+++ b/asm/parser.c
@@ -463,6 +463,12 @@ restart_parse:
         if (i == ':') {         /* skip over the optional colon */
             i = stdscan(NULL, &tokval);
         } else if (i == 0) {
+            /*!
+             *!orphan-labels [on] labels alone on lines without trailing `:'
+             *!  warns about source lines which contain no instruction but define
+             *!  a label without a trailing colon. This is most likely indicative
+             *!  of a typo, but is technically correct NASM syntax (see \k{syntax}.)
+             */
             nasm_warnf(WARN_ORPHAN_LABELS | ERR_PASS1,
                        "label alone on a line without a colon might be in error");
         }