From: "Task Struct From Hell" <taskstructfromhell@googlemail.com>
To: ninjaboy <n0b0dyn1nj4@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: c preprocessor expansion
Date: Fri, 9 Jan 2009 08:15:13 +0000 [thread overview]
Message-ID: <ef37ea20901090015i3d4ae177k5d587125ab0b212f@mail.gmail.com> (raw)
In-Reply-To: <a3399010901081011p607d688es98a4ca77581b0a88@mail.gmail.com>
On Thu, Jan 8, 2009 at 6:11 PM, ninjaboy <n0b0dyn1nj4@gmail.com> wrote:
> 2009/1/8 Task Struct From Hell <taskstructfromhell@googlemail.com>:
>> Hi,
>>
>> I was wondering if gcc has any argument which allows for the expansion
>> of all macros in a file, just so if we have something like the
>> following:
>>
>>
>> #define FOO "bar"
>>
>> int main() {
>> printf(FOO);
>> }
>>
>> It will output this:
>>
>> int main() {
>> printf("bar");
>> }
>>
>
> gcc -E code.c -o codemacro.m
Cheers for all responses so far!
prev parent reply other threads:[~2009-01-09 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 17:49 c preprocessor expansion Task Struct From Hell
2009-01-08 17:46 ` Nicholas Mc Guire
2009-01-08 17:53 ` Yan Lin
2009-01-08 18:11 ` ninjaboy
2009-01-09 8:15 ` Task Struct From Hell [this message]
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=ef37ea20901090015i3d4ae177k5d587125ab0b212f@mail.gmail.com \
--to=taskstructfromhell@googlemail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=n0b0dyn1nj4@gmail.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;
as well as URLs for NNTP newsgroup(s).