[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#5950: defvaralias after defvar should be warned in runtime
From: |
Clément Pit-Claudel |
Subject: |
bug#5950: defvaralias after defvar should be warned in runtime |
Date: |
Thu, 2 Aug 2018 10:37:25 -0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 |
On 2018-08-02 09:28, Noam Postavsky wrote:
> On 2 August 2018 at 09:08, Clément Pit-Claudel <cpitclaudel@gmail.com> wrote:
>
>>> Usually the warning is due to the defvaralias call being performed after
>>> the corresponding `defvar`s.
>>
>> Right. But why is that a problem?
>
> The typical failure case goes like this, user does this:
>
> (setq the-package-setting 'foo)
> (require 'the-package)
>
> And the-package.el does this:
>
> (defvar the-package-real-setting 'bar)
> ;; Oops! User's setting of `foo' is overwritten here:
> (defvaralias 'the-package-setting 'the-package-real-setting)
Thanks. Should the warning be disabled when both variables are already
`defvar'd, then?
Clément.
- bug#5950: defvaralias after defvar should be warned in runtime, Noam Postavsky, 2018/08/01
- bug#5950: defvaralias after defvar should be warned in runtime, Clément Pit-Claudel, 2018/08/02
- bug#5950: defvaralias after defvar should be warned in runtime, Noam Postavsky, 2018/08/02
- bug#5950: defvaralias after defvar should be warned in runtime,
Clément Pit-Claudel <=
- bug#5950: defvaralias after defvar should be warned in runtime, Stefan Monnier, 2018/08/02
- bug#5950: defvaralias after defvar should be warned in runtime, Clément Pit-Claudel, 2018/08/02
- bug#5950: defvaralias after defvar should be warned in runtime, Noam Postavsky, 2018/08/03
- bug#5950: defvaralias after defvar should be warned in runtime, Clément Pit-Claudel, 2018/08/03
- bug#5950: defvaralias after defvar should be warned in runtime, Noam Postavsky, 2018/08/03
- bug#5950: defvaralias after defvar should be warned in runtime, Clément Pit-Claudel, 2018/08/03
- bug#5950: defvaralias after defvar should be warned in runtime, Stefan Monnier, 2018/08/03