[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] docs: more details about make VPATH rewriting woes

From: Stefano Lattarini
Subject: Re: [PATCH] docs: more details about make VPATH rewriting woes
Date: Thu, 15 Sep 2011 11:21:16 +0200
User-agent: KMail/1.13.7 (Linux/2.6.30-2-686; KDE/4.6.5; i686; ; )

On Thursday 15 September 2011, Ralf Wildenhues wrote:

> * Stefano Lattarini wrote on Wed, Sep 14, 2011 at 11:35:37AM CEST:

> > On Wednesday 14 September 2011, Ralf Wildenhues wrote:

> > > It applies to any word that is surrounded by whitespace (or beginning or

> > > end of command line), regardless of shell syntax. Please don't

> > > formulate it like Solaris make would understand shell syntax when

> > > rewriting rules, IMHO that's confusing and makes it harder to understand

> > > the issue.

> > >

> > You're right, my previous formulation was somewhat confusing in this

> > regard. What about the squash-in below?


> Fine with me, thanks.


Should I take this as an ACK to push?

> > address@hidden, which is typically undesirable. In fact, @command{make} is

> > +completely unaware of shell syntax used in the rules, so the VPATH

> > +rewrite can potentially apply to @emph{any} whitespace-separated word

> > +in a rule -- including shell variables, functions, and keywords.


> I think you want a comma rather than an emdash here;


You're right. Consider this fixed.

> also, for American

> English type setting, you'd write an emdash as three hyphens and no

> space right before and afterwards,


That is just horribly ugly IMHO, almost as bad as a final dot inside

double quotes. I refuse to voluntarily use those formatting in the

text I write :-) I went for the comma instead.

> as texinfo markup.


> Cheers,

> Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]