summaryrefslogtreecommitdiff
path: root/error.c
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2005-09-29 13:04:26 +0000
committerSimon Tatham <anakin@pobox.com>2005-09-29 13:04:26 +0000
commit4a4d009cbba73b06e8b16fdf8f8f59e712a4bc6f (patch)
treebd35d0b7ede0517d9e223ddcaf66b0984ba684fa /error.c
parente1a1d840b82db8a3b93e112e94e55f761c2b6dba (diff)
downloadhalibut-4a4d009cbba73b06e8b16fdf8f8f59e712a4bc6f.zip
halibut-4a4d009cbba73b06e8b16fdf8f8f59e712a4bc6f.tar.gz
halibut-4a4d009cbba73b06e8b16fdf8f8f59e712a4bc6f.tar.bz2
halibut-4a4d009cbba73b06e8b16fdf8f8f59e712a4bc6f.tar.xz
Remove the error message `no text found in paragraph'. Aaron Brown
points out that it's perfectly possible to generate an empty paragraph using legal Halibut syntax: a paragraph containing nothing but a \#{...} comment will do the job, and is quite likely to happen if you've commented out a load of Halibut code. Therefore, an empty paragraph is now silently ignored rather than being an error condition in itself; if you create an empty paragraph due to it containing an unrecognised directive, then you'll get an error for _that_ and only that. [originally from svn r6361]
Diffstat (limited to '')
-rw-r--r--error.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/error.c b/error.c
index b1e74a1..3635f0f 100644
--- a/error.c
+++ b/error.c
@@ -278,11 +278,6 @@ static void do_error(int code, va_list ap) {
flags = FILEPOS;
sfree(sp);
break;
- case err_emptypara:
- fpos = *va_arg(ap, filepos *);
- sprintf(error, "found no text in paragraph");
- flags = FILEPOS;
- break;
case err_whatever:
sp = va_arg(ap, char *);
vsprintf(error, sp, ap);