Re: [PATCH v2 05/16] Add BVAR_DEFAULT for access to buffer defaults

[Eli Zaretskii]

> From: Spencer Baugh <sbaugh@catern.com>
> Date: Sat, 21 Nov 2020 21:34:34 -0500
> Cc: Spencer Baugh <sbaugh@catern.com>, Arnold Noronha <arnold@tdrhq.com>,
>  Stefan Monnier <monnier@iro.umontreal.ca>, Dmitry Gutov <dgutov@yandex.ru>
> 
> This is more direct. This macro can stay as an lvalue even when we
> change BVAR to be a function call - directly changing and accessing
> buffer_defaults is always fine.

I think it will be confusing to have BVAR that cannot be an lvalue,
and BVAR_DEFAULT that can.  It will lead to mistakes and frustration.
If we want to be able to assign to Vstandard_category_table etc.,
let's invent some internal way of doing that, but without exposing a
macro whose name is similar to BVAR.

(Log message is missing.)

Thanks.