From 7787f2ad56717a073c3288cd112e165eda10bc43 Mon Sep 17 00:00:00 2001 From: Richard Brooksby Date: Fri, 31 May 2013 19:19:08 +0100 Subject: [PATCH] Fixing up some code snippet formatting. Copied from Perforce Change: 182372 ServerID: perforce.ravenbrook.com --- mps/design/guide.impl.c.format.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/mps/design/guide.impl.c.format.txt b/mps/design/guide.impl.c.format.txt index 36e2e6b9016..18ebb1badd1 100644 --- a/mps/design/guide.impl.c.format.txt +++ b/mps/design/guide.impl.c.format.txt @@ -94,10 +94,10 @@ particular the following are deprecated:: case 0: f = inRampMode ? AMCGen0RampmodeFrequency : AMCGen0Frequency; _`.statement.one.why`: Debuggers can often only place breakpoints on lines, -not expressions or statements within a line. The `if (thing) return;` is +not expressions or statements within a line. The ``if (thing) return;`` is a particularly important case, if thing is a reasonably rare return condition then you might want to breakpoint it in a debugger session. -Annoying because `if (thing) return;` is quite compact and pleasing +Annoying because ``if (thing) return;`` is quite compact and pleasing otherwise. Indentation @@ -107,7 +107,7 @@ _`.indent`: Indent the body of a block by two spaces. For formatting purposes, the "body of a block" means: - statements between braces, -- a single statement following a lone if; +- a single statement following a lone ``if``; - statements in a switch body; see .switch. (_`.indent.logical`: The aim is to group what we think of as logical