This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC 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: #define in a macro definition

From: Brian Dessent <brian at dessent dot net>
To: gcc-help at gcc dot gnu dot org
Date: Sun, 18 Dec 2005 09:15:20 -0800
Subject: Re: #define in a macro definition
References: <43A4E5EE.602@micromotive.net> <43A4FA74.A29C713B@dessent.net> <43A51885.3070405@gmail.com> <43A52138.325D2E7F@dessent.net> <43A546BB.2000908@gmail.com>

bill wrote:

(please keep replies on-list)

> Because what's happening is that I'm dumpster diving code, and coming
> accross
> constants and wondering what their value is.  So I'm constantly adding to
> the list of constants that get printed.  Each time, I have to type or
> cut/paste 3 lines:

There's much better ways to do that then.  For example, "gcc -E -dM
yourfile.c".

Brian

References:
- #define in a macro definition
  - From: Samuel J. Guido
- Re: #define in a macro definition
  - From: Brian Dessent
- Re: #define in a macro definition
  - From: bill
- Re: #define in a macro definition
  - From: Brian Dessent

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