Resolve issue73 where quotes in character would trigger string state

[boyter]

A fix for #73

If a " was used inside a character it would trigger the string state. Quick fix is to check for \ before it and stay in the code state.

Long term fix is to have a state for dealing with quotes, perhaps inside strings as they have the same rules. However this requires updating the whole JSON document and checking that quotes work like strings in all languages (unlikely). This seems like a good reasonable short term fix for most C like languages.

[dbaggerman]

I'm a little concerned that not all languages follow exactly the same quoting rules, and hardcoding the backslash like this might break other languages.

PowerShell for example uses a backtick rather than a backslash to escape characters, as far as I'm aware.

There are also cases like backtick strings in Go, where escape characters can't be used at all.

fmt.Println(`\`)

will print \

[boyter]

Absolutely. Its a short term thing that should catch most cases for C like languages but can then be improved with #76 This is to get it in place then improve. I also want to change the return from the states to a struct now because its getting hard to read, but thats also going on that other branch.

In your Go example it would hit the string state first and be counted correctly so no issues there thankfully.

Certainly not intending to get this into a release, however it lays the ground work for the other branch.

[dbaggerman]

Agreed that it probably isn't ready for a release as is, but as a starting point it's fine.