discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: mdocml, ERROR: argument count wrong: multi-line arguments > 0 (have 0)
Date: Fri, 06 Aug 2010 19:43:26 +0200	[thread overview]
Message-ID: <4C5C49BE.7040500@bsd.lv> (raw)
In-Reply-To: <20100806163410.GO80306@acme.spoerlein.net>

>> Hi
>>
>> I think that Qq, Dq, Sq, Aq, Bq can have 0 arguments:
>>
>> Error log:
>> man/man1/c99.1:
>> <stdin>:99:5: ERROR: argument count wrong: multi-line arguments > 0 (have 0)
>> <stdin>:108:5: ERROR: argument count wrong: multi-line arguments > 0 (have 0)
>> Man source:
>> man/man1/c99.1:
>> (http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.bin/c99/c99.1)
>> 99:5:.Pq Qq
>> 108:5:.Pq Aq ,
>> Man:
>> headers whose names are enclosed in double-quotes ("") will be
>> brackets (<>), the header will be searched for only in
>>
>> Error log:
>> man/man1/bsdtar.1:
>> <stdin>:357:2: ERROR: argument count wrong: multi-line arguments > 0 (have 0)
>> <stdin>:359:2: ERROR: argument count wrong: multi-line arguments > 0 (have 0)
>> Man source:
>> man/man1/bsdtar.1:
>> (http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.bin/tar/bsdtar.1)
>> 357:2:.Qq
>> 359:2:.Qq .
>> Man:
>> This is equivalent to --uname "" --gname "".  On extract, it
>>
>> Error log:
>> /tmp/man.yg1LX62VGM/usr/share/man/man3/getloadavg.3:
>> <stdin>:51:16: ERROR: argument count wrong: multi-line arguments > 0 (have 0)
>> Man source:
>> man/man3/getloadavg.3:
>> (http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/gen/getloadavg.3)
>> 51:16:.Fa loadavg Ns Bq .
>> Man:
>> retrieved and assigned to successive elements of loadavg[].  The system
> 
> These were fixed in FreeBSD -HEAD a couple of days ago, the cgi web
> stuff is usually from some older -RELEASE however.
> 
> Not sure this helps in any way ...

You're correct in that these macros should have the lowest warning 
category.  The ERROR class is used, by convention, only when input might 
screw formatting but can be processed anyway.  These are more or less 
harmless.  (By the way, these aren't fatal errors, so you're only seeing 
this if you're using -Wall and it's only bombing if you're using 
-Werror, too.)

Thanks!

Kristaps
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-08-06 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06 13:55 Alex Kozlov
2010-08-06 16:34 ` Ulrich Spörlein
2010-08-06 17:43   ` Kristaps Dzonsons [this message]
2010-08-06 21:05 Alex Kozlov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C5C49BE.7040500@bsd.lv \
    --to=kristaps@bsd.lv \
    --cc=discuss@mdocml.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).