delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2004/02/04/15:28:27

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Wed, 04 Feb 2004 20:25:11 +0200
From: "Eli Zaretskii" <eliz AT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp AT delorie DOT com
Message-Id: <3405-Wed04Feb2004202510+0200-eliz@elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to: <20040204080948.20033.00001476@mb-m17.aol.com> (sterten@aol.com)
Subject: Re: array indices [i][j]
References: <uptcv9jmy DOT fsf AT elta DOT co DOT il> <20040204080948 DOT 20033 DOT 00001476 AT mb-m17 DOT aol DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> From: sterten AT aol DOT com (Sterten)
> Newsgroups: comp.os.msdos.djgpp
> Date: 04 Feb 2004 13:09:48 GMT
> 
> I assume that the compiler first translates the #define 's
> into another  source code file  S  and then processes
> S in a second step.

In effect, it does (in practice, the two phases run together).

> So, can I code with macros and then make the compiler
> output the preprocessed file S also, so that everyone
> can have the source without macros, if he wants ?

You can (see the -E switch to the compiler), but why would you like
to?

My recommendation is: when in Rome behave as a Roman.  That is, when
you work in a certain programming language, use the syntactic
conventions of that programming language, even if facilities like
macros allow you to redefine almost everything.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019