Yes. And many people here doesn’t seem to get that.

I’m not a dev of any kind. I occasionally write some bash and awk scriots to automate some things and if I need some kind of plain text (non-binary) data format I prefer tsv over json.

So why do I still get this? Is it just that many json advocates want to make sure others know json does support other data types than plain string?

Holy unholiness, Batman!

I did expect those kinds of tricks would cause syntax error in #defines, but instead looks like everything is allowed… Some day someone #defines a such abomination that it creates universe wide black hole -like vacuum and everything ceases to exist.

I’m not a C programmer (is this code even C?), but I anticipated seeing comments like this. 😂