summaryrefslogtreecommitdiff
path: root/doc
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 /doc
parenta8d4f4b24af589104ef0746bd35a40fd186327fb (diff)
downloadnasm-fc869bac3dbd26f92c2f7b2c1641669baf742e26.tar.gz
Visual C++ error format needs <space>:<space> after the parentheses.
Diffstat (limited to 'doc')
-rw-r--r--doc/nasmdoc.src6
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index 2ac98c39..e00311c2 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.