[Top][All Lists]

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

Re: PATCH: patsubst support

From: Alex Hornby
Subject: Re: PATCH: patsubst support
Date: Sat, 28 Oct 2000 11:15:54 +0100 (BST)

Alexandre Oliva writes:
 > On Oct 27, 2000, Akim Demaille <address@hidden> wrote:
 > > Yep, by default Automake must not let the users do nonportable
 > > things.
 > I tend to agree.  But I wouldn't say `must not', I'd say `should not'.

What is the policy regarding changes to non-portable behavour?

Current CVS autoconf will pass through patsubst style variables to to
Makefile for dynamic expansion via make. I have now got a patch that
expands these statically which I need to decide to the default for. I
have illustrated the possible default behavours with a

# fragment
FOO = foo bar
BAR = ${FOO:%=%.c}

a) default static expansion to on, this is good for portability 

# fragment
FOO = foo bar
BAR = foo.c bar.c

b) default static expansion to off, avoids surprising anyone depending 
   on dynamic expansion by make, retains the same non-portable
   default behavour as current CVS.

# fragment
FOO = foo bar
BAR = ${FOO:%=%.c}

What do people think?


reply via email to

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