Re: [PATCH 00/11] support "%define variable {value}"

[Akim Demaille]

Le 4 avr. 2013 à 17:36, Akim Demaille <address@hidden> a écrit :

> What follows is a first, incomplete, step.  It is incomplete because
> there are not enough tests, the documentation is not properly updated,
> and NEWS is not changed.  The options -D/-F also need to become
> brace-aware, and maybe quotes aware.  The M4 code should start to
> "typecheck" some of the values (e.g., it should warn for
> %define api.namespace "foo" instead of {foo}).  But before going
> any further, I'd like to receive opinions, obviously especially
> Joel's :)
> 
> Akim Demaille (11):
>  muscle: minor refactoring
>  style: comment changes
>  muscle: refactor
>  grammar: split %union to group together related aspects
>  grammar: style changes
>  regen
>  style: fix comments
>  grammar: record the kind of %define variable values
>  regen
>  grammar: do not add a \n at the end of blocks of code
>  api.namespace: demonstrate and use {...} values instead of "..."
>    values

I have installed these patches (in master).  Not because they are mature,
but because my current branch about api.value.type is becoming
too hard to maintain, so I prefer to flush what's already good
enough (Joel's comments show that we have similar opinions, so
if changes are needed, they will be more adjustments than full
rewrite).  Yet, more tests, doc and NEWS are needed.  This will
be covered.