[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Unexpected failure in tricky use of eval
From: |
Paul Smith |
Subject: |
Re: Unexpected failure in tricky use of eval |
Date: |
Sun, 13 May 2012 15:45:00 -0400 |
On Sat, 2012-05-12 at 19:42 +0200, Stefano Lattarini wrote:
> BTW: to make it more easy to discover at make runtime whether the bug has
> been fixed in the make version in use, could a proper new entry be added
> to .FEATURES? Maybe 'can-have-lazy-variables'? (I know, I suck at choosing
> names).
I'm not interested in having the features option used to describe bugs
that have been fixed, sorry. It should be straightforward to find some
real feature added in the release where the bug is fixed though and you
can check for that instead.
> Better again: would you consider the possibility of adding a new kind
> of variables (let's call them "lazy"), so that a definition like:
>
> LAZYVAR = val
>
> behaves exactly as:
>
> LAZYVAR = $(override LAZYVAR := val)$(LAZY)
I don't have any idea what this is supposed to do... it doesn't make any
sense as written. Can you describe in words what you're looking for?
- Unexpected failure in tricky use of eval, Stefano Lattarini, 2012/05/12
- Re: Unexpected failure in tricky use of eval, Eldar Abusalimov, 2012/05/12
- Re: Unexpected failure in tricky use of eval, Stefano Lattarini, 2012/05/12
- Re: Unexpected failure in tricky use of eval, Stefano Lattarini, 2012/05/12
- "Lazy" variables in GNU make (was: Re: Unexpected failure in tricky use of eval), Stefano Lattarini, 2012/05/13
- Re: Unexpected failure in tricky use of eval,
Paul Smith <=
- Re: Unexpected failure in tricky use of eval, Stefano Lattarini, 2012/05/13
- Re: Unexpected failure in tricky use of eval, Paul Smith, 2012/05/14
- Re: Unexpected failure in tricky use of eval, Stefano Lattarini, 2012/05/14