Re: [Json] Doofus Parameter Labels

[Wendy Roome <[e-mail]>]

It would help if you told us which draft and which code generator you are
using.

My first reaction is that if the code generator is supposed to generate
real code that you can feed directly into a compiler, then the code
generator should ensure that it generates legal code. Eg, if it maps a
protocol field into a variable, the code gen should transmogrify the
protocol field name into a valid variable name. Simplest solution is to
slap a fixed prefix, like m_, onto every generated variable, and replace
non-alpha-num chars with _.

My second reaction is why can¹t you do that yourself?

	- Wendy Roome


On 03/30/2015, 15:38, "Phillip Hallam-Baker" <[e-mail]> wrote:

>So, I am implementing an IETF draft which is fairly widely used and
>using a code generator to speed things along.
>
>The code is breaking because the spec has decided to use 'protected'
>as a tag which is of course a reserved keyword in Java, C# and much
>else.
>
>OK so there is an escape feature that I can use instead. But those
>don't exist in other languages. And then I come across a tag that has
>a non alphanumeric tag value.
>
>
>This sort of thing is likely to be happening quite a bit now that
>people are using JSON and it would be a lot better if we could avoid
>it. The fact that JSON allows tags to be any valid UNICODE sequence
>does not mean that all choices are equal.
>
>In general it would be good if people writing specs could stick to the
>identifier naming rules for C and avoid reserved words from Java, C#,
>etc. The languages and tools I use are quite capable of using accented
>characters. I have absolutely no clue how to generate them on the
>keyboard though.
>
>_______________________________________________
>json mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/json