Re: multiline output variables.

2005-01-17 Thread Stepan Kasal
Hello, this sounds very interesting. I admit I don't fully understand your code so please forgive me any errors in the following comments: On Thu, Jan 13, 2005 at 05:49:36PM -0500, Dan Manthey wrote: > It appears to me that since the set of substitutions is fixed at the time > of running autocon

Re: Using $bindir in configure.ac

2005-01-17 Thread Stepan Kasal
Hi, On Fri, Jan 14, 2005 at 04:49:54PM +0100, Peter Simons wrote: > I have applied the last patch you sent to the macro and ... > dnl @author Stepan Kasal <[EMAIL PROTECTED]>, ... Thanks. Perhaps we should give credit to Andreas, too. There is still one problem with the macro--it changes prefix

Re: Using $bindir in configure.ac

2005-01-17 Thread Peter Simons
Stepan Kasal writes: > There is still one problem with the macro--it changes > prefix=NONE to prefix="$ac_default_prefix", so subsequent > macros don't have the information whether prefix is > defaulted or not. > The patch attached to this mail fixes this issue. I have applied the patch mom

Re: multiline output variables.

2005-01-17 Thread Dan Manthey
On Mon, 17 Jan 2005, Stepan Kasal wrote: > Hello, > > You decided to use 2), which is the most correct solution. Unfortunately, > the performance penalty may be high. I'm afraid it's to high to be worth it. Yeah, that's what I was afraid of. > > I think that if we choose a sufficiently unusu

Re: multiline output variables.

2005-01-17 Thread Noah Misch
On Mon, Jan 17, 2005 at 11:13:11AM +0100, Stepan Kasal wrote: > On Fri, Jan 14, 2005 at 02:56:16AM -0800, Noah Misch wrote: > > s/[^t]$/&\\/ does not do the job? > > I don't think so. What if the substituted value were "first\nsecond"? > The newline wouldn't get escaped. Oops. I stopped thinkin