[jamming] Unclear parts of the Jam sematics - Alen Ladavac - com.perforce.jamming

17 messages in com.perforce.jamming[jamming] Unclear parts of the Jam se...

From	Sent On	Attachments
Wallace, Richard	24 Sep 2003 12:38
Harri Porten	24 Sep 2003 13:37
Wallace, Richard	24 Sep 2003 15:21
Paul Forgey	24 Sep 2003 16:38
Alen Ladavac	28 Sep 2003 05:01
Arnt Gulbrandsen	29 Sep 2003 02:08
Arnt Gulbrandsen	29 Sep 2003 02:49
Vladimir Prus	29 Sep 2003 03:00
Alen Ladavac	29 Sep 2003 04:41
Vladimir Prus	29 Sep 2003 05:03
Arnt Gulbrandsen	29 Sep 2003 05:11
Vladimir Prus	29 Sep 2003 05:20
Johan Nilsson	29 Sep 2003 05:38
Johan Nilsson	29 Sep 2003 05:58
Alen Ladavac	29 Sep 2003 06:51
Alen Ladavac	29 Sep 2003 08:13
Christopher Seiwald	29 Sep 2003 16:35

Subject:	[jamming] Unclear parts of the Jam sematics
From:	Alen Ladavac (al...@croteam.com)
Date:	09/29/2003 06:51:34 AM
List:	com.perforce.jamming

Looking at the source, it seems like $(VAR:E) is the same as $(VAR:E=).

If it was, then it would be unneeded, because that is the default: if var is not set, it evaluates to an empty var, doesn't it? Why would the original Jamfile use it, then?

Alen

----- Original Message ----- From: "Vladimir Prus" <gho...@cs.msu.su> To: "Arnt Gulbrandsen" <ar...@gulbrandsen.priv.no>; "Alen Ladavac" <al...@croteam.com> Cc: <jamm...@perforce.com> Sent: Monday, September 29, 2003 10:01 AM Subject: Re: [jamming] Unclear parts of the Jam sematics

Arnt Gulbrandsen wrote:

HDRSEARCH on $(>) = $(SEARCH_SOURCE:E) $(SUBDIRHDRS) $(HDRS) $(STDHDRS) ;

What is that supposed to mean?

No idea.

(I'm getting ready to flame someone for making :E and :E= confusingly similar while different in function, though...)

Looking at the source, it seems like $(VAR:E) is the same as $(VAR:E=).

- Volodya