discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: Giving up on emulating SYNOPSIS vspace.
Date: Tue, 8 Jun 2010 02:06:46 +0200	[thread overview]
Message-ID: <20100608000646.GE8550@iris.usta.de> (raw)
In-Reply-To: <4C0D83E1.5040500@bsd.lv>

Hi Kristaps,

Kristaps Dzonsons wrote on Tue, Jun 08, 2010 at 01:42:25AM +0200:
> Ingo Schwarze wrote:

>> 2) global variables
>> -------------------
>> Consider /usr/src/lib/libc/rpc/svc.3:
>>
>>  .Ft int
>>  .Fn svc_destroy "SVCXPRT *xprt"
>>  .Ft struct pollfd *
>>  .Fa svc_pollfd ;
>>  .Ft int
>>  .Fa svc_max_pollfd ;
>>  .Ft fd_set
>>  .Fa svc_fdset ;
>>  .Ft fd_set
>>  .Fa *__svc_fdset ;
>>  .Ft int
>>  .Fa __svc_fdsetsize ;
>>  .Ft int
>>  .Fa svc_fds ;
>>  .Ft int
>>  .Fn svc_freeargs "SVCXPRT *xprt" "xdrproc_t inproc" "char *in"
>>
>> I think this is acceptable usage; probably using .Va instead of .Fa
>> would be a bit better, but apart from that, i wouldn't know how to
>> express this in a better way.  (NB, it wasn't RPC variable naming
>> conventions i was trying to praise here... ;-)

> `Vt' is documented for use in this case.

Right, and i tried that, but being documented is not the same as
being in working order.  This is what both old and new grow spit out
when you switch to .Vt/.Va:

     struct pollfd *
     svc_pollfd;
     int
     svc_max_pollfd;
     fd_set
     svc_fdset;
     fd_set
     *__svc_fdset;
     int
     __svc_fdsetsize;
     int
     svc_fds;

Not quite what we want...  :-/

[...]
>> So, i'm going to commit this to OpenBSD, we can fix the two minor
>> issues presented above in tree, either now or later.

> Can you commit fixes to BSD.lv as well?

Er, frankly, no, i meant i'm going commit your reorg, i don't have
patches for the issues (1) and (2) yet.  But as this concerns a very
small number of pages and all that goes awry is a few missing
blank lines, we can add these patches whenever we have them.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-06 23:18 Kristaps Dzonsons
2010-06-06 23:42 ` Jason McIntyre
2010-06-07 11:12   ` Kristaps Dzonsons
2010-06-07 23:26     ` Ingo Schwarze
2010-06-07 23:42       ` Kristaps Dzonsons
2010-06-08  0:06         ` Ingo Schwarze [this message]
2010-06-08  9:13           ` OT: Vt vs. Ft/Fn (WAS: Giving up on emulating SYNOPSIS vspace.) Kristaps Dzonsons
2010-06-08 10:02             ` Thomas Klausner
2010-06-08 12:06               ` Kristaps Dzonsons
2010-06-12 18:05                 ` Vt vs. Ft/Fn Ingo Schwarze
2010-06-07  0:35 ` Giving up on emulating SYNOPSIS vspace 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=20100608000646.GE8550@iris.usta.de \
    --to=schwarze@usta.de \
    --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).