summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorH. Peter Anvin <hpa@zytor.com>2002-06-10 00:41:41 +0000
committerH. Peter Anvin <hpa@zytor.com>2002-06-10 00:41:41 +0000
commitfc869bac3dbd26f92c2f7b2c1641669baf742e26 (patch)
treee21eb25fe5f6a6e3efe2a8154e03e95fb91c5d5f
parenta8d4f4b24af589104ef0746bd35a40fd186327fb (diff)
downloadnasm-fc869bac3dbd26f92c2f7b2c1641669baf742e26.tar.gz
nasm-fc869bac3dbd26f92c2f7b2c1641669baf742e26.tar.bz2
nasm-fc869bac3dbd26f92c2f7b2c1641669baf742e26.zip
Visual C++ error format needs <space>:<space> after the parentheses.
-rw-r--r--doc/nasmdoc.src6
-rw-r--r--nasm.c4
2 files changed, 4 insertions, 6 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index 2ac98c3..e00311c 100644
--- a/doc/nasmdoc.src
+++ b/doc/nasmdoc.src
@@ -544,8 +544,7 @@ Currently, two error reporting formats may be selected. They are
the \c{-Xvc} option and the \c{-Xgnu} option. The GNU format is
the default and looks like this:
-\c filename.asm:65: error:specific error message
-
+\c filename.asm:65: error: specific error message
where \c{filename.asm} is the name of the source file in which the
error was detected, \c{65} is the source file line number on which
@@ -556,8 +555,7 @@ detailed text message which should help pinpoint the exact problem.
The other format, specified by \c{-Xvc} is the style used by Microsoft
Visual C++ and some other programs. It looks like this:
-\c filename.asm(65) error:specific error message
-
+\c filename.asm(65) : error: specific error message
where the only difference is that the line number is in parentheses
instead of being delimited by colons.
diff --git a/nasm.c b/nasm.c
index 84c2bc5..987573c 100644
--- a/nasm.c
+++ b/nasm.c
@@ -1411,7 +1411,7 @@ static void report_error_gnu (int severity, const char *fmt, ...)
* This function prints an error message to error_file in the
* style used by Visual C and some other Microsoft tools. An example
* would be:
- * c:\project\file.asm(50) error: blah blah blah
+ * c:\project\file.asm(50) : error: blah blah blah
* where c:\project\file.asm is the full path of the file,
* 50 is the line number on which the error occurs (or is detected)
* and "error:" is one of the possible optional diagnostics -- it
@@ -1434,7 +1434,7 @@ static void report_error_vc (int severity, const char *fmt, ...)
char * currentfile = NULL;
long lineno = 0;
src_get (&lineno, &currentfile);
- fprintf (error_file, "%s(%ld) ", currentfile, lineno);
+ fprintf (error_file, "%s(%ld) : ", currentfile, lineno);
nasm_free (currentfile);
}
va_start (ap, fmt);