Re: Default lexical-binding to t

[Stefan Monnier <monnier@iro.umontreal.ca>]

>> They should likely add a `lexical-binding:nil` cookie and move on.
> In each and every file?

Yup.

> Not a simple thing to do.

It doesn't require any thought, so I consider it simple.
Also, there shouldn't be so terribly many such files remaining nowadays.

But if experience shows it to be a problem, I guess we could provide
a command that automates it.

>> Of course, they can also change this cookie to `t` temporarily every
>> once in a while to see if it uncovers a problem or not, so the
>> conversion can be done bit by bit.
> For some code that gets executed only rarely, this is not practical.

I don't see why.

> Can you tell what are the benefits of turning on lexical-binding by
> default, relative to what we have now?

IME, nowadays lexbind is the "de facto" default used for all
new ELisp code, including code snippets posted around the web.
So using dynbind when there's no cookie is often a source of errors
and confusion.


        Stefan