[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: |
Mon, 14 May 2012 11:10:08 -0400 |
On Mon, 2012-05-14 at 00:14 +0200, Stefano Lattarini wrote:
> >> 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.
> >
> In fact, it should have been s/$(LAZY)/$(LAZYVAR)/. Sorry for the confusion.
It still doesn't make sense to me. There is no function "override"...?
Did you mean $(eval override LAZYVAR := val) maybe?
> > Can you describe in words what you're looking for?
> >
> Basically, a new kind of assignment that do not expand the right-hand side
> at definition time, but which causes the value the variable expands to the
> first time it gets dereferenced to be cached, and reused in any successive
> expansion of that same variable.
I see. I know of other variants of make that have this type of
assignment.
- 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, 2012/05/13
- 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/14