[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#20241: 25.0.50; `setq' with only one argument
From: |
Glenn Morris |
Subject: |
bug#20241: 25.0.50; `setq' with only one argument |
Date: |
Mon, 23 Nov 2015 13:44:51 -0500 |
User-agent: |
Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) |
Alan Mackenzie wrote:
>> setq' should not be called with only one argument. It "works", with the
>> effect of assigning a value of nil, but it is poor form. Typically this
>> is a sign of a typo.
>
> Fixed in emacs-25. The interpreter now signals a wrong-number-of-args
> error, and the byte compiler issues a warning.
What on earth is this incompatible change doing in a feature-frozen
release branch?
Also, the combination of a compiler _warning_ and a run-time _error_
makes no sense.
- bug#20241: 25.0.50; `setq' with only one argument, Alan Mackenzie, 2015/11/23
- bug#20241: 25.0.50; `setq' with only one argument,
Glenn Morris <=
- bug#20241: 25.0.50; `setq' with only one argument, Glenn Morris, 2015/11/23
- bug#20241: 25.0.50; `setq' with only one argument, Alan Mackenzie, 2015/11/23
- bug#20241: 25.0.50; `setq' with only one argument, Alan Mackenzie, 2015/11/24
- bug#20241: 25.0.50; `setq' with only one argument, Glenn Morris, 2015/11/24
- bug#20241: 25.0.50; `setq' with only one argument, Alan Mackenzie, 2015/11/24
- bug#20241: 25.0.50; `setq' with only one argument, Artur Malabarba, 2015/11/24
- bug#20241: 25.0.50; `setq' with only one argument, Alan Mackenzie, 2015/11/24
- bug#20241: 25.0.50; `setq' with only one argument, John Wiegley, 2015/11/24
- bug#20241: 25.0.50; `setq' with only one argument, Alan Mackenzie, 2015/11/25