Linux Manual Pages development
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: noname <noname-CuI0ZDT4mYnsrOwW+9ziJQ@public.gmane.org>,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: "Writing" instead of "Warning" in dlopen(3) manpage
Date: Thu, 2 Jan 2014 14:45:16 -0500	[thread overview]
Message-ID: <201401021445.17586.vapier@gentoo.org> (raw)
In-Reply-To: <CAKgNAkjeDs21b36mULBF6VFQeoKeVOEDnRj=7GPTmchci-xDzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: Text/Plain, Size: 1096 bytes --]

On Thursday 02 January 2014 14:20:50 Michael Kerrisk (man-pages) wrote:
>     /* According to the ISO C standard, casting between function
>        pointers and 'void *', as done above, produces undefined results.
>        POSIX.1-2003 and POSIX.1-2008 accepted this state of affairs and
>        proposed the following workaround:
> 
>            *(void **) (&cosine) = dlsym(handle, "cos");
> 
>        This (clumsy) cast conforms with ISO C standard and will avoid
>        any compiler warnings.

"with the ISO C standard"

>        The 2013 Technical Corrigendum to POSIX.1-2008 (a.k.a.
>        POSIX.1-2013)

i thought you wanted to avoid "a.k.a." ?  or does that not apply to 
parenthetical asides too ?

should all these random preferences be added in man-pages(7) ?  off the top of 
my head:
	- userspace vs user space vs user-space
	- a.k.a. / e.g. / i.e. usage
	- NUL usage (or lack thereof)
	- HISTORY should be a .SS of NOTES
	- wrapping based on periods/commas
	- preference for 75 cols

some of these could even be checks added to scripts/ ...
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-01-02 19:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-31 12:42 "Writing" instead of "Warning" in dlopen(3) manpage noname-CuI0ZDT4mYnsrOwW+9ziJQ
2013-12-31 16:19 ` Mike Frysinger
     [not found]   ` <201312311119.55754.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2014-01-02  1:46     ` Michael Kerrisk (man-pages)
     [not found]       ` <52C4C513.7020509-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-02  4:06         ` Mike Frysinger
     [not found]           ` <201401012306.40108.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2014-01-02  9:33             ` Michael Kerrisk (man-pages)
     [not found]               ` <CAKgNAkjYTw3_BGQKwVNyfs-rLmxgVMiH4hBy_gBm=9DpvSHnFA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-02 12:33                 ` Mike Frysinger
     [not found]                   ` <201401020733.11627.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2014-01-02 19:20                     ` Michael Kerrisk (man-pages)
     [not found]                       ` <CAKgNAkjeDs21b36mULBF6VFQeoKeVOEDnRj=7GPTmchci-xDzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-02 19:45                         ` Mike Frysinger [this message]
     [not found]                           ` <201401021445.17586.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2014-01-03  2:51                             ` Michael Kerrisk (man-pages)

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=201401021445.17586.vapier@gentoo.org \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=noname-CuI0ZDT4mYnsrOwW+9ziJQ@public.gmane.org \
    /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