Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] doc/gdbint.texinfo: Fix problems with ``{'' and ``}''
Date: Fri, 18 Oct 2002 11:57:00 -0000	[thread overview]
Message-ID: <1021018185728.ZM10332@localhost.localdomain> (raw)

I've just committed (as obvious) the patch below.

It fixes errors when running "make info" -- I had been doing "make pdf",
thinking that would catch all of the problems.

	* gdbint.texinfo (Address Classes): Fix problems with insertion
	of ``{'' and ``}'' in example.

Index: doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.105
diff -u -p -r1.105 gdbint.texinfo
--- doc/gdbint.texinfo	17 Oct 2002 18:33:36 -0000	1.105
+++ doc/gdbint.texinfo	18 Oct 2002 18:48:51 -0000
@@ -2675,34 +2675,34 @@ to implement the address class macros:
 @smallexample
 somearch_address_class_type_flags (int byte_size,
                                    int dwarf2_addr_class)
-{
+@{
   if (byte_size == 2)
     return TYPE_FLAG_ADDRESS_CLASS_1;
   else
     return 0;
-}
+@}
 
 static char *
 somearch_address_class_type_flags_to_name (int type_flags)
-{
+@{
   if (type_flags & TYPE_FLAG_ADDRESS_CLASS_1)
     return "short";
   else
     return NULL;
-}
+@}
 
 int
 somearch_address_class_name_to_type_flags (char *name,
                                            int *type_flags_ptr)
-{
+@{
   if (strcmp (name, "short") == 0)
-    {
+    @{
       *type_flags_ptr = TYPE_FLAG_ADDRESS_CLASS_1;
       return 1;
-    }
+    @}
   else
     return 0;
-}
+@}
 @end smallexample
 
 The qualifier @code{@@short} is used in @value{GDBN}'s type expressions


                 reply	other threads:[~2002-10-18 18:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1021018185728.ZM10332@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox