Dear R-devel team,
Many thanks for the great resource that is "Writing R Extensions"!
I noticed two occurrences of "his", one to refer to the R package user, another
to refer to the R package author. Folks in these two groups are not all men, so
I suggest changing the word to "their" to make it gender-neutral. Attached is a
patch for your consideration.
Thanks for your time, best regards,
Maëlle.
Index: doc/manual/R-exts.texi
===================================================================
--- doc/manual/R-exts.texi (revision 76557)
+++ doc/manual/R-exts.texi (working copy)
@@ -3450,7 +3450,7 @@
outputs in the package sources it is not necessary that these can be
re-built at install time, i.e., the package author can use private @R{}
packages, screen snapshots and @LaTeX{} extensions which are only
-available on his machine.@footnote{provided the conditions of the
+available on their machine.@footnote{provided the conditions of the
package's license are met: many, including @acronym{CRAN}, see the
omission of source components as incompatible with an Open Source
license.}
@@ -4538,7 +4538,7 @@
Under no circumstances should your compiled code ever call @code{abort}
or @code{exit}@footnote{or where supported the variants @code{_Exit} and
@code{_exit}.}: these terminate the user's @R{} process, quite possibly
-including all his unsaved work. One usage that could call @code{abort}
+including all their unsaved work. One usage that could call @code{abort}
is the @code{assert} macro in C or C++ functions, which should never be
active in production code. The normal way to ensure that is to define
the macro @code{NDEBUG}, and @command{R CMD INSTALL} does so as part of
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
