On Fri, Jan 7, 2022 at 11:32 AM Dmitry Goncharov
wrote:
> If we can agree, then i'll file a request to opengroup to explicitly
> state that this
>
> "When an escaped is found in a command line in a makefile,
> the command line shall contain the , the , and the
> next line, except that the first c
Quoth Dmitry Goncharov:
Humm, in the following example do you want N and M to expand to
different values? If yes, can you please tell us about your use case
where such behavior is needed?
.POSIX:
M=word
N=${M:word=a\
b}
all:; echo ${N} ${M:word=a\
b}
I would think they should expand to differe
On Fri, Dec 24, 2021 at 6:30 PM Humm wrote:
> That’s the argument I’m making.
Humm, in the following example do you want N and M to expand to
different values? If yes, can you please tell us about your use case
where such behavior is needed?
.POSIX:
M=word
N=${M:word=a\
b}
all:; echo ${N} ${M:wo
On Fri, 2021-12-24 at 23:30 +, Humm wrote:
> (woops, sorry for replying off-list first; mutt doesn’t like me)
>
> Quoth Paul Smith:
> > In your example the backslash is part of a variable expansion: it's
> > INSIDE the variable expansion so it will be handled by make as part
> > of expanding t
(woops, sorry for replying off-list first; mutt doesn’t like me)
Quoth Paul Smith:
In your example the backslash is part of a variable expansion: it's
INSIDE the variable expansion so it will be handled by make as part of
expanding the variable and won't ever be passed to the shell.
POSIX.1-20
On Fri, 2021-12-24 at 10:45 +, Humm wrote:
> Consider the Makefile:
>
> .POSIX:
> M = word
> all:
> echo ${M:word=a\
> b}
>
> I believe, as the escaped newline is in a command line, the expected
> behavior is to let the macro expand to i
(I’m not subscribed to the list.)
Consider the Makefile:
.POSIX:
M = word
all:
echo ${M:word=a\
b}
I believe, as the escaped newline is in a command line, the expected
behavior is to let the macro expand to it, and thus to run the command
