After reading the long section about how to use 'extern inline' with gnulib,
the question surely comes up: what about 'static inline'? Why does it not
have a gnulib module?
Let me answer this in the documentation.
2019-03-19 Bruno Haible <br...@clisp.org>
doc: Document how to use 'static inline'.
* doc/static-inline.texi: New file.
* doc/gnulib.texi: Include it.
diff --git a/doc/gnulib.texi b/doc/gnulib.texi
index 802e39b..ac3d570 100644
--- a/doc/gnulib.texi
+++ b/doc/gnulib.texi
@@ -6373,6 +6373,7 @@ to POSIX that it can be treated like any other Unix-like
platform.
* Safe Allocation Macros::
* Compile-time Assertions::
* Integer Properties::
+* static inline::
* extern inline::
* Closed standard fds::
* Container data types::
@@ -6403,6 +6404,8 @@ to POSIX that it can be treated like any other Unix-like
platform.
@include intprops.texi
+@include static-inline.texi
+
@include extern-inline.texi
@include xstdopen.texi
diff --git a/doc/static-inline.texi b/doc/static-inline.texi
new file mode 100644
index 0000000..035c023
--- /dev/null
+++ b/doc/static-inline.texi
@@ -0,0 +1,20 @@
+@c GNU static-inline module documentation
+
+@c Copyright (C) 2019 Free Software Foundation, Inc.
+
+@c Permission is granted to copy, distribute and/or modify this document
+@c under the terms of the GNU Free Documentation License, Version 1.3
+@c or any later version published by the Free Software Foundation;
+@c with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
+@c Texts. A copy of the license is included in the ``GNU Free
+@c Documentation License'' file as part of this distribution.
+
+@node static inline
+@section Static inline functions
+
+@cindex static inline
+@cindex inline
+
+In order to mark functions as @code{static inline}, the only
+prerequisite you need is an @code{AC_REQUIRE([AC_C_INLINE])}.
+No Gnulib module is needed.
