Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Taylor <dtaylor@emc.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: stabs.texinfo update for macro define/undefine
Date: Wed, 01 Nov 2006 03:21:00 -0000	[thread overview]
Message-ID: <200611010305.kA135iYx019864@mailhub.lss.emc.com> (raw)
In-Reply-To: Your message of "Tue, 31 Oct 2006 15:23:29 PST."              <m3odrsoyry.fsf@codesourcery.com>

> From: Jim Blandy <jimb@codesourcery.com>
> Date: Tue, 31 Oct 2006 15:23:29 -0800
> 
> It's clear from the example, but it would be nice if the text
> explicitly explained how function-like macro arguments appear in the
> N_MAC_DEFINE stabs.  It also should explain how the following are
> distinguished:
> 
> #define foo x
> #define foo() x
> 
> With the latter #definition, 'foo' followed by something other than an
> opening parenthesis isn't replaced.

The former shows up as "foo x", the latter as "foo() x".

Yes, the example could be enhanced to illustrate that.  And a little
more about the ``transformation'' from what is found in the *.c file
to the stabs entry.

But, as to the latter -- am I misunderstanding you?  Are you asking
for text about when something is replaced versus when it isn't
replaced?  If yes, that is *WAY* beyond the scope of the file.  The
file deals exclusively with *STABS*.  When something is replaced vs
not replaced is a CPP issue.  It has nothing to do with STABS.


  reply	other threads:[~2006-11-01  3:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200610251931.k9PJVRDO011265@mailhub.lss.emc.com>
     [not found] ` <ud58guoa6.fsf@gnu.org>
2006-10-30 22:25   ` David Taylor
2006-10-31  4:19     ` Eli Zaretskii
2006-10-31 14:18       ` David Taylor
2006-10-31 22:39         ` Eli Zaretskii
2006-10-31 23:23     ` Jim Blandy
2006-11-01  3:21       ` David Taylor [this message]
2006-11-01 19:32         ` Jim Blandy

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=200611010305.kA135iYx019864@mailhub.lss.emc.com \
    --to=dtaylor@emc.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.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