[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master c7d2a0d: * lisp/emacs-lisp/benchmark.el (benchmark-run): Allo
|
From: |
Stefan Monnier |
|
Subject: |
Re: master c7d2a0d: * lisp/emacs-lisp/benchmark.el (benchmark-run): Allow variable. |
|
Date: |
Tue, 27 Mar 2018 16:06:15 -0400 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
>> What's the intended meaning of this nil?
> I assume nil means 1. Doesn't seem particularly sensible, but there you go.
Until now it didn't: it was taken as an instruction to execute, i.e.
(benchmark-run nil (setq m (1+ 0)))
is treated as
(benchmark-run 1 (progn nil (setq m (1+ 0))))
rather than
(benchmark-run 1 (setq m (1+ 0)))
It just happens to do the same. The same holds for
(benchmark-run (+ 3 4) (setq m (1+ 0)))
which behaves like
(benchmark-run 1 (+ 3 4) (setq m (1+ 0)))
> Whatever happens, benchmark-run and benchmark-run-compiled should be
> consistent.
Oh, right, I did miss this one, thanks,
Stefan