[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Propagating local variables?
From: |
Shea Levy |
Subject: |
Re: Propagating local variables? |
Date: |
Fri, 18 May 2018 16:15:50 -0400 |
Maybe a good transition path is to add an explicit (opt-in) parent
buffer mechanism when creating a buffer, and adding a hook when a buffer
is created *without* explicitly setting the parent (or explicitly
setting it to null) so the user can plug their own heuristics in until
legacy modules catch up.
John Wiegley <address@hidden> writes:
>>>>>> Richard Stallman <address@hidden> writes:
>
>> * specify, when creating a buffer, what parent buffer (if any) it should
>> have.
>
>> I think the second way will be better controlled, because it won't depend on
>> heuristics.
>
> I think so too, except that it won't work well with legacy modules, if they
> weren't written with such inheritance in mind.
>
> --
> John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
> http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
signature.asc
Description: PGP signature
Re: Propagating local variables?, Richard Stallman, 2018/05/16
Re: Propagating local variables?, Shea Levy, 2018/05/17
Re: Propagating local variables?, Philipp Stephani, 2018/05/19