Using empty $(else) variable for readability

2015-10-17 Thread Tony Theodore
Hi, I’m looking at tidying up some existing makefile logic and noticed there isn’t a lot of consistency in the format of conditionals - especially from myself over the years. We use make for build automation, not directly for compilation, and don’t use any pre-processor conditionals in this con

Re: Using empty $(else) variable for readability

2015-10-17 Thread Paul Smith
On Sat, 2015-10-17 at 22:40 +1100, Tony Theodore wrote: > Is this a reasonable idea and is there any chance $(else) will have > some defined value in the future? "else" as a variable will never have another value. The POSIX standard for make reserves variables that start with "." and are all capi

Re: Using empty $(else) variable for readability

2015-10-17 Thread Rakesh Sharma
Tony Theodore me.com> writes: > > When there is an `else` in a complex section, it sometimes looks like: > > $(if , \ > \ > , \ > ) > > These can be deeply nested and the dangling `, \` can get really hard to parse. Constructs like: > > $(if , \ > \ >