From: Nate Eldredge <neldredge AT hmc DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: where is __FILE__/__DATE__ ?
Date: 18 Aug 2000 16:52:58 -0700
Organization: Posted via Supernews, http://www.supernews.com
Lines: 38
Sender: nate AT mercury DOT bitbucket
Message-ID: <83lmxum8it.fsf@mercury.bitbucket>
References: <o9glpsk29ic6nhovs8rr6siagp9a2o38dv AT 4ax DOT com> <1u6ops46pog5cggn1o102tlig0msdqkmeo AT 4ax DOT com>
X-Complaints-To: newsabuse AT supernews DOT com
User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Radical NetSurfer <radsmail AT juno DOT com> writes:

> On Wed, 16 Aug 2000 12:36:42 -0400, Radical NetSurfer
> <radsmail AT juno DOT com> wrote:
> 
> >Does DJGPP suppport __FILE__, __DATE__, __LINE__, etc?
> 
> Apparently these do exist, since when I 
> #define __FILE__ foo_bar
> I get a re-definition error....
> 
> I still have NO CLUE how to get these to display during compile 
> times.  I think it rediculuous that #message does not exist,
> or that #warning does not expand macro's.
> Thats why people use Borland, etc.

You are at liberty to do so.  However, I suspect the demand for these
features is not as high as you think.  An awful lot of people use gcc,
and I've never before seen anybody complain about not having these
features.

But as I said, gcc AT gnu DOT org are the people to convince.

> PLEASE if you can provide a REAL, working example
> for how GCC, or a MAKE file, can display the actual
> date, time of Compile, please show me. THANKS.

In a Makefile:

%.o : %.c
        echo Now compiling $<
        date
        gcc $(CFLAGS) -o $@ $<

-- 

Nate Eldredge
neldredge AT hmc DOT edu