This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: stabs.texinfo update for macro define/undefine


> cc: gdb-patches@sourceware.org
> Date: Tue, 31 Oct 2006 09:18:03 -0500
> From: David Taylor <dtaylor@emc.com>
> 
> You mentioned it, but I guess I misunderstood.  I ran both `make dvi'
> and `make info' and looked at the resulting files.  The info file
> stayed in fewer than 80 columns; I didn't see any TeX complaints about
> an overfull hbox, nor did the dvi file have a black box on any of
> those lines.  So, I guessed that they looked too long but were
> actually okay.

Maybe due to whitespace TeX succeeded to squeeze them in.

> In the future, how should I test to make sure that the lines are not
> too long?

Any line longer than 64 characters in an @example should be shortened.

> For this, how about:
> 
>     @example
>         .stabs  "NONE 42",54,0,1,0
>         .stabs  "TWO(a,b) (a + (a) + 2 * b)",54,0,2,0
>         .stabs  "ONE(c) (c + 19)",54,0,3,0
>         .stabs  "ONE",58,0,10,0
>         .stabs  "ONE(c) (c + 23)",54,0,11,0
>     @end example
> 
>     NOTE: In the example above, @code{54} is @code{N_MAC_DEFINE} and @code{58}
>     is @code{N_MAC_UNDEF}.
> 
> ?  This is the text in the patch attached below.

This is fine; it's exactly what I was suggesting.

> > With these changes, this can go in.  Thanks.
> 
> Thanks.  I don't have write after approval privileges.

I committed the patch for you.  Thanks again for working on this.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]