doc/: Use the correct notation for `->' arrows.

I'm still not entirely sure I want to get into this pretty-printing
game, but this way I can at least make the decision in a single place.

diff --git a/doc/concepts.tex b/doc/concepts.tex
index c938c47cd91333aafea938cccffaf64cb510c98a..b8637e8157cb1dece084a0ea0543de8cd630669d 100644 (file)
--- a/doc/concepts.tex
+++ b/doc/concepts.tex
@@ -281,7 +281,7 @@ about these slot members: C code can access them in the usual way.
 For example, if @|MyClass| has the nickname @|mine|, and defines a slot @|x|
 of type @|int|, then the simple function
 \begin{prog}
 For example, if @|MyClass| has the nickname @|mine|, and defines a slot @|x|
 of type @|int|, then the simple function
 \begin{prog}

-  int get_x(MyClass *m) \{ return (m->mine.x); \}
+  int get_x(MyClass *m) \{ return (m@->mine.x); \}

 \end{prog}
 will extract the value of @|x| from an instance of @|MyClass|.
 
 \end{prog}
 will extract the value of @|x| from an instance of @|MyClass|.
 


@@ -355,9 +355,9 @@ function using @|malloc| might work as follows.
 \begin{prog}
   void *new_instance(const SodClass *c) \\
   \{ \\ \ind
 \begin{prog}
   void *new_instance(const SodClass *c) \\
   \{ \\ \ind

-    void *p = malloc(c->cls.initsz); \\
+    void *p = malloc(c@->cls.initsz); \\

     if (!p) return (0); \\
     if (!p) return (0); \\

-    c->cls.init(p); \\
+    c@->cls.init(p); \\

     return (p); \- \\
   \}
 \end{prog}
     return (p); \- \\
   \}
 \end{prog}

diff --git a/doc/tutorial.tex b/doc/tutorial.tex
index afc6109d339557e8fb08e3fc21a3a90c45a179ad..bb357d84ec9810e215db0ba569090ce011bca196 100644 (file)
--- a/doc/tutorial.tex
+++ b/doc/tutorial.tex
@@ -84,7 +84,7 @@ The main consequences of this are as follows.
   hostile to object-oriented programming as it ever was.  This means that
   you'll end up writing ugly things like
   \begin{prog}
   hostile to object-oriented programming as it ever was.  This means that
   you'll end up writing ugly things like
   \begin{prog}

-    thing->_vt->foo.frob(thing, mumble);
+    thing@->_vt@->foo.frob(thing, mumble);

   \end{prog}
   fairly frequently.  This can be made somewhat less painful using macros,
   but we're basically stuck with C.  The upside is that you know exactly what
   \end{prog}
   fairly frequently.  This can be made somewhat less painful using macros,
   but we're basically stuck with C.  The upside is that you know exactly what


@@ -197,7 +197,7 @@ bizarre looking runes.  Let's take it one step at a time.
 allocates space for an instance of class @"Greeter".  We're not going to use
 this space directly.  Instead, we do this frightening looking thing.
 \begin{prog}
 allocates space for an instance of class @"Greeter".  We're not going to use
 this space directly.  Instead, we do this frightening looking thing.
 \begin{prog}

-  Greeter *g = Greeter__class->cls.init(\&g_obj);
+  Greeter *g = Greeter__class@->cls.init(\&g_obj);

 \end{prog}
 Taking it slowly: @"Greeter__class" is a pointer to the object that
 represents our class @"Greeter".  This object contains a member, named
 \end{prog}
 Taking it slowly: @"Greeter__class" is a pointer to the object that
 represents our class @"Greeter".  This object contains a member, named


@@ -208,7 +208,7 @@ the instance, which we use in preference to grovelling about in the
 
 Having done this, we `send the instance a message':
 \begin{prog}
 
 Having done this, we `send the instance a message':
 \begin{prog}

-  g->_vt->greeter.greet(g, stdout);
+  g@->_vt@->greeter.greet(g, stdout);

 \end{prog}
 This looks horrific, and seems to repeat itself quite unnecessarily.  The
 first @"g" is the recipient of our `message'.  The second is indeed a copy of
 \end{prog}
 This looks horrific, and seems to repeat itself quite unnecessarily.  The
 first @"g" is the recipient of our `message'.  The second is indeed a copy of