discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Paul A. Patience" <paul@apatience.com>
To: discuss@mandoc.bsd.lv
Subject: .Fn alternative for parenthesis-less function syntax
Date: Sat, 12 Mar 2022 01:05:55 +0000	[thread overview]
Message-ID: <87h786w3og.fsf@apatience.com> (raw)
In-Reply-To: <87h786w3og.fsf@apatience.com>


Hello,

What would be the best way to document a library function for a
programming language that doesn't require parentheses after the function
when invoked?
For example TCL, Lisp dialects, OCaml, Haskell and others.
It would be weird to see in such manual pages the function name followed
by parentheses.
(Though perhaps a price worth paying?)

One possibility would be .Ic, because many of these programming
languages have an interactive interpreter and thus functions could be
considered internal commands.

Best regards,
Paul

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


           reply	other threads:[~2022-03-12  1:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87h786w3og.fsf@apatience.com>]

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=87h786w3og.fsf@apatience.com \
    --to=paul@apatience.com \
    --cc=discuss@mandoc.bsd.lv \
    --subject='Re: .Fn alternative for parenthesis-less function syntax' \
    /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).