[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/5] Remove parser/location global variable setup
|
From: |
Carl Sorensen |
|
Subject: |
Re: [PATCH 1/5] Remove parser/location global variable setup |
|
Date: |
Sat, 30 May 2015 19:13:23 +0000 |
|
User-agent: |
Microsoft-MacOutlook/14.5.0.150423 |
On 5/30/15 12:51 PM, "David Kastrup" <address@hidden> wrote:
>David Kastrup <address@hidden> writes:
>
>At any rate: huh. I propose getting rid of a 10-year old syntactic
>artifact and the only response are naming convention enquiries. I mean:
>good to know that there are still developers alive.
>
>I still think it may have the potential of issue 2883 where its general
>availability lagged behind people becoming used to it.
This is far enough over my head that I don't feel qualified to comment on
it.
Based on what I saw, it looks very useful.
I love the idea of getting rid of arbitrary variables that the user cannot
change (parser and location).
I trust you to do the right thing. You've demonstrated that you can and
will.
So I guess this means LGTM, but I suppose that is not worth much coming
from me.
Thanks,
Carl
- [PATCH 1/5] Remove parser/location global variable setup, David Kastrup, 2015/05/27
- [PATCH 2/5] Fix various jumbled parser/location argument pairs, David Kastrup, 2015/05/27
- [PATCH 3/5] Remove parser/location args from music function calls, David Kastrup, 2015/05/27
- [PATCH 4/5] convert-ly rule for removing parser/location, David Kastrup, 2015/05/27
- [PATCH 5/5] Run scripts/auxiliar/update-with-convert-ly.sh, David Kastrup, 2015/05/27
- Re: [PATCH 1/5] Remove parser/location global variable setup, David Kastrup, 2015/05/27
- Re: [PATCH 1/5] Remove parser/location global variable setup, Dan Eble, 2015/05/27