[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #30606] mysterious behavior from $(if)
From: |
Timothy N Murphy |
Subject: |
[bug #30606] mysterious behavior from $(if) |
Date: |
Fri, 30 Jul 2010 19:22:54 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:2.0b3pre) Gecko/20100723 Minefield/4.0b3pre |
Follow-up Comment #2, bug #30606 (project make):
Hi,
The $(call) expands everything, so you get this:
lets say $1=ab
b := ab
yn := n
vs := ab:
You might ask why :-)
Well when the $(if) is expanded by call, b has no value - the assignment has
not been executed yet because your exec happens *after* your call.
You need to protect things such that the call can't expand them prematurely.
e.g. $1 doesn't really need protection but you do need $$(if and $$(strip
$$(b)) and $$(yn)
Cheers,
Tim
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30606>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #30606] mysterious behavior from $(if), Reinier Post, 2010/07/30
- [bug #30606] mysterious behavior from $(if), Reinier Post, 2010/07/30
- [bug #30606] mysterious behavior from $(if),
Timothy N Murphy <=
- [bug #30606] mysterious behavior from $(if), Paul D. Smith, 2010/07/30
- [bug #30606] mysterious behavior from $(if), Reinier Post, 2010/07/30
- [bug #30606] mysterious behavior from $(if), Paul D. Smith, 2010/07/30
- [bug #30606] mysterious behavior from $(if), Paul D. Smith, 2010/07/30
- [bug #30606] mysterious behavior from $(if), Timothy N Murphy, 2010/07/30