Follow-up Comment #1, bug #54630 (project make):
Another example is the advice not to omit parens in references to
single-character variables: "you could reference the variable x with ‘$x’.
However, this practice is strongly discouraged, except in the case of the
automatic variables..." I've found
_X/light.kmz noise.kmz
B: X_X_X_X/light.kmz X_X_X_X/noise.kmz
You're already off the rails, so I haven't tried to understand the rest of
your email. If you're going to post to many people what you think is a bug,
please cut your example down to the smallest, simplest thing that
demonstrat
Can be done with functions, e.g., the second prereq is $(word 2,$+). Given
that it’s straightforward composition of documented features, you’d want to
document it only if it were very commonly needed. Which it isn’t. That’s my
two cents, anyway.
Sam
On Fri, Jun 14, 2019 at 11:29 PM Dan Jacobson
I'd like to raise some questions that I think any proposal ought to answer.
I'll assume a straw man proposal: there's one function, and it takes one of
the following forms:
$(math OPERATOR,VALUE1,VALUE2)
$(math OPERATOR,VALUE1)
A binary operator (first form) is one of + - * and /. The only unary
> I suggest that
> a) $HOME/.local/include is effectively added to the
>include_directories ...
If two users build the same source tree, they will effectively be building
variants of it, each extending it with her own $HOME/.local/include
directory. And if one user builds two *different* sourc
On Tue, Jun 2, 2020 at 10:19 AM Paul Smith wrote:
> On Tue, 2020-06-02 at 08:48 -0400, Sam Kendall wrote:
> > > I suggest that
> > > a) $HOME/.local/include is effectively added to the
> > >include_directories ...
> >
> > If two users build the
Follow-up Comment #5, bug #52209 (project make):
I strongly agree with the need but suggest a different syntax:
$(eq lhs,rhs)
$(neq lhs,rhs)
Each function expands lhs and rhs. If the results are identical or
nonidentical, respectively, the function expands to T. Otherwise, it expands
to empty.
