>From 3c752419a442afc8d6763ca0e46f77fd8ee14efe Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Fri, 5 Aug 2016 21:03:23 +0900
Subject: [PATCH 3/5] Add \nbco{} command for code snippet without line break
This commit also replaces an instance of \co{} command in
formal/ppcmem.tex with the \nbco{} command
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
formal/ppcmem.tex | 2 +-
perfbook.tex | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/formal/ppcmem.tex b/formal/ppcmem.tex
index cf637ad..c5ec6ed 100644
--- a/formal/ppcmem.tex
+++ b/formal/ppcmem.tex
@@ -96,7 +96,7 @@ In the example, line~1 identifies the type of system (``ARM'' or ``PPC'')
and contains the title for the model. Line~2 provides a place for an
alternative name for the test, which you will usually want to leave
blank as shown in the above example. Comments can be inserted between
-lines~2 and~3 using the OCaml (or Pascal) syntax of \co{(* *)}.
+lines~2 and~3 using the OCaml (or Pascal) syntax of \nbco{(* *)}.
Lines~3-6 give initial values for all registers; each is of the form
\co{P:R=V}, where \co{P} is the process identifier, \co{R} is the register
diff --git a/perfbook.tex b/perfbook.tex
index 34059e0..35d6ced 100644
--- a/perfbook.tex
+++ b/perfbook.tex
@@ -61,6 +61,7 @@
\makeatother
% --- End of workaround for Fedora 23 Texlive bug
\newcommand{\co}[1]{\lstinline[breaklines=true,breakatwhitespace=true]{#1}}
+\newcommand{\nbco}[1]{\lstinline[breaklines=false,breakatwhitespace=false]{#1}}
\title{Is Parallel Programming Hard, And, If So, What Can You Do About It?}
\author{
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
