wrong and unclear conditional syntax documentation

2019-03-22 Thread Britton Kerin
The manual says: The syntax of the conditional-directive is the same whether the conditional is simple or complex; after an else or not. There are four different directives that test different conditions. Here is a table of them: ifeq (arg1, arg2) ifeq 'arg1' 'arg2' ifeq "arg1" "arg2" ifeq "arg1"

Re: gmake + unexec = fast!

2019-03-22 Thread Stefan Monnier
> On the hardware of the day, it took 30 seconds for GNU Make > 3.80 to read the files and issue the first build command. Do you have some idea of how those 30s were spent? > So then I took the "unexec" code from GNU Emacs, transplanted it into > GNU Make and hooked it to a "--dump" option. > Now

Re: wrong and unclear conditional syntax documentation

2019-03-22 Thread Paul Smith
On Fri, 2019-03-22 at 10:59 -0800, Britton Kerin wrote: > It's also unclear what is different about the conditions being > tested. Different levels of interpolation? There is no difference other than the delimiters used. arg1 and arg2 are treated identically in all cases. I don't really know wh

Re: wrong and unclear conditional syntax documentation

2019-03-22 Thread Eli Zaretskii
> From: Britton Kerin > Date: Fri, 22 Mar 2019 10:59:30 -0800 > > The manual says: > > The syntax of the conditional-directive is the same whether the > conditional is simple or complex; after an else or not. There are four > different directives that test different conditions. Here is a table >

Re: gmake + unexec = fast!

2019-03-22 Thread Kaz Kylheku (gmake)
On 2019-03-22 12:07, Stefan Monnier wrote: On the hardware of the day, it took 30 seconds for GNU Make 3.80 to read the files and issue the first build command. Do you have some idea of how those 30s were spent? No detailed breakdown; just reading per-directory make include files, and perform