On 18.08.26 12:00, Heikki Linnakangas wrote:
> This seems hacky. Can we change BuildTupleFromCStrings() to take a const
> instead? Maybe that was part of your "difficult half" already?
>
> I guess that requires changing all the callers: You get a warning if
> pass a "char **" to a "const char **". Is there a way with some macro
> magic or something that you could accept both?
>
> All else look good to me at a quick glance.
I have committed these patches except the one above. I have an idea for
that, but I'll prepare that separately.