The use of \IXacrmfst{} macro changes the resulting sentence from:
... to use the object-oriented "resource allocation is
initialization" (RAII) pattern [...].
to:
... to use the object-oriented \emph{resource-allocation-is-
initialization} (RAII} pattern [...].
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
glsdict.tex | 2 ++
locking/locking.tex | 4 ++--
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/glsdict.tex b/glsdict.tex
index c861e09b..7f7ae336 100644
--- a/glsdict.tex
+++ b/glsdict.tex
@@ -229,6 +229,8 @@
\newacronym{numa}{NUMA}{non-uniform memory architecture}
\newacronym{qsbr}{QSBR}{quiescent-state-based reclamation}
\newabbreviation{qsbr:m}{QSBR}{quiescent-state-based-reclamation}
+\newacronym{raii}{RAII}{resource allocation is initialization}
+\newabbreviation{raii:m}{RAII}{resource-allocation-is-initialization}
\newacronym{rcu}{RCU}{read-copy update}
\newacronym{smp}{SMP}{symmetric multiprocessing}
\newabbreviation{smp:m}{SMP}{symmetric-multiprocessing}
diff --git a/locking/locking.tex b/locking/locking.tex
index 2a6068a7..851a1f00 100644
--- a/locking/locking.tex
+++ b/locking/locking.tex
@@ -1571,8 +1571,8 @@ compared to VAX/VMS's six.
The locking primitives discussed thus far require explicit acquisition and
release primitives, for example, \co{spin_lock()} and \co{spin_unlock()},
respectively.
-Another approach is to use the object-oriented ``resource allocation
-is initialization'' (RAII) pattern~\cite{MargaretAEllis1990Cplusplus}.\footnote{
+Another approach is to use the object-oriented \IXacrmfst{raii}
+pattern~\cite{MargaretAEllis1990Cplusplus}.\footnote{
Though more clearly expressed at
\url{https://www.stroustrup.com/bs_faq2.html\#finally}.}
This pattern is often applied to auto variables in languages like C++,
--
2.17.1
