Path: csiph.com!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: Effect of CPP tags
Date: Fri, 29 Dec 2023 10:33:26 -0800
Organization: None to speak of
Lines: 17
Message-ID: <87o7e8voy1.fsf@nosuchdomain.example.com>
References: <umet9d$3hir9$1@dont-email.me> <umlba2$iq0h$3@dont-email.me> <ummhnp$rf7k$1@dont-email.me> <ummmqe$s4od$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Info: dont-email.me; posting-host="429276411a044e69398eca77c4a97f98"; logging-data="983545"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/WZLLDjfEutcfB/3R3MsrH"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Cancel-Lock: sha1:/amMVKYD+lmZS8eJmeiaM5blZRo= sha1:+g+j304bSDlotxYBfAlO8qaKxIk=
Xref: csiph.com comp.lang.c:379680

David Brown <david.brown@hesbynett.no> writes:
> A useful tool that someone might like to write for this particular
> situation would be a partial C preprocessor, letting you choose what 
> gets handled.  You could choose to expand the code here for, say,
> _GNU_SOURCE and _BSD_SOURCE - any use of these in #ifdef's and 
> conditional compilation would be expanded according to whether you
> have defined the symbols or not, leaving an output that is easier to 
> understand while keeping most of the pre-processor stuff unchanged (so
> not affecting #includes, and leaving #define'd macros and constants 
> untouched and therefore more readable).

The unifdef tool does some of this.  (I haven't used it much.)

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */