https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262001

--- Comment #5 from Graham Perrin <grahamper...@freebsd.org> ---
Created attachment 241402
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=241402&action=edit
Screenshot: part of the FreeBSD Developers' Handbook

<https://docs.freebsd.org/en/books/developers-handbook/ipv6/#_sockaddr_storage>
(pictured) was found through a lazy (inaccurate) run of: 

rg __ /usr/doc


Many results, this chunk below caught my eye as things sped past. 

A better search should yield more useful results. 

I'll not yet give thought to what must be done with .po files. 

----

/usr/doc/documentation/content/en/books/developers-handbook/ipv6/_index.po
1471:"sockaddr_storage members are named.  One proposal is to prepend \"__\" to
"
1472:"the members (like \"__ss_len\") as they should not be touched.  The other
"
1487:"\t\tu_char\t__ss_len;\t/* address length */\n"
1488:"\t\tu_char\t__ss_family;\t/* address family */\n"
1541:"have -Dss_family=__ss_family to unify all occurrences (including header "
1542:"file) into __ss_family, or"
1547:msgid "never touch __ss_family. cast to sockaddr * and use sa_family
like:"

/usr/doc/documentation/content/en/books/developers-handbook/ipv6/_index.adoc
617:One proposal is to prepend "__" to the members (like "__ss_len") as they
should not be touched.
626:            u_char  __ss_len;       /* address length */
627:            u_char  __ss_family;    /* address family */
651:. have -Dss_family=__ss_family to unify all occurrences (including header
file) into __ss_family, or
652:. never touch __ss_family. cast to sockaddr * and use sa_family like:

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to