Eric Blake <ebl...@redhat.com> writes: > On 08/08/2018 07:03 AM, Markus Armbruster wrote: >> The JSON parser optionally supports interpolation. The code calls it >> "escape". Awkward, because it uses the same term for escape sequences >> within strings. The latter usage is consistent with RFC 7159 "The >> JavaScript Object Notation (JSON) Data Interchange Format" and ISO C. >> Call the former "interpolation" instead. >> >> Signed-off-by: Markus Armbruster <arm...@redhat.com> >> --- >> include/qapi/qmp/json-lexer.h | 2 +- >> qobject/json-lexer.c | 64 +++++++++++++++++------------------ >> qobject/json-parser.c | 8 ++--- >> 3 files changed, 37 insertions(+), 37 deletions(-) > > Mechanical, and a worthwhile name change. > > Reviewed-by: Eric Blake <ebl...@redhat.com> > > Bike-shedding: Would INTERP (short for interpolate) be any more > legible than INTERPOL (which I first read as short for 'international > police')?
Ah, where's the fun in that! When I read INTERP, I associate "interpreter". On the other hand, there appears to be precedence for abbreviating "interpolate" / "interpolation" to "interp" in numpy and MATLAB. Another possible abbreviation would be IPOLATE.
