discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Yuri Pankov <yuripv@yuripv.net>
To: mandoc-discuss <discuss@mandoc.bsd.lv>
Subject: "WARNING: parenthesis in function name" correctness
Date: Tue, 10 Sep 2019 11:20:24 +0300	[thread overview]
Message-ID: <421eeed3-8da5-b852-4581-1058de113831@yuripv.net> (raw)

I'm looking into fixing sbuf.9 which currently has somewhat unreadable:

.Ft typedef\ int ( sbuf_drain_func ) ( void\ *arg, const\ char\ *data, 
int\ len ) ;

...into somewhat nicer:

.Ft typedef int
.Fo (sbuf_drain_func)
.Fa "void *arg"
.Fa "const char *data"
.Fa "int len"
.Fc

...but that gives me a:

mandoc: share/man/man9/sbuf.9:69:5: WARNING: parenthesis in function 
name: (sbuf_drain_func)

Looking at the code, parenthesis are only allowed in the following form:

.Ft (*func_ptr)

...while here we don't have a "*" -- it's the way it's typedef'ed in the 
source, and I want to follow it, so I wonder if that check/warning is 
really useful.
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv

             reply	other threads:[~2019-09-10  8:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10  8:20 Yuri Pankov [this message]
2019-09-10 17:47 ` Ingo Schwarze
2019-09-10 22:43   ` Yuri Pankov
2019-09-13 19:31     ` Ingo Schwarze

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=421eeed3-8da5-b852-4581-1058de113831@yuripv.net \
    --to=yuripv@yuripv.net \
    --cc=discuss@mandoc.bsd.lv \
    --subject='Re: "WARNING: parenthesis in function name" correctness' \
    /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

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).