Hi, Makers!
i just discovered a Make behaviour which really surprises me. While that
in itself is nothing new ;), this one certainly violates the principal
of least astonishment:
When a $(warning) or $(error) is inside a 'define', it is evaluated even
if it is part of a comment. A demonstratio
On Wednesday 20 June 2007, Philip Guenther wrote:
> On 6/19/07, Stephan Beal <[EMAIL PROTECTED]> wrote:
> Okay, so you've defined a variable, 'bogo', whose value consists of
> two lines, the first of which has a '#' as its first non-whitespace
> charact
On Wednesday 20 June 2007, Paul Smith wrote:
> the variable being defined. In fact nothing is parsed inside a
> define. I'm not sure, from your message, if this is what you feel is
> the surprising behavior;
Right - that's what surprised me. i assumed that comments were skipped
during the init
ror 1
vs
2 errors generated.
Makefile:75: recipe for target 'obj/fsl_vfile.o' failed
(Not a problem, of course, but wasn't sure which version your comment
assumes is the basis for comparison.)
PS: i like that the line number is now shown!
--
- stephan beal
http://wan
Please excuse the non-bug post to bug-make@..., but I didn't find
another address for the make tool, and 'make@' bounced...
-- Forwarded Message --
Subject: make: you guys are gawds
Date: Wed, 9 May 2001 17:04:06 +0200
From: Stephan Beal <[EMAIL PROT
