Quote mangling in TCC

[Charles Dye]

What's going on here?

C:\>set test=%@char[8220 8220 8220 8220]

C:\>echo %@ascii[%test]
34 8220 8220 8220

C:\>

I can only guess. Perhaps TCC temporarily hides the first quote in a string by replacing it with 0x201C before some sensitive operation, then changing it back afterwards? If it's something like that, may I suggest using a noncharacter like 0xFDEF instead?

 

[vefatica]

I wonder if TCC is treating the first one as a real (opening) double quote (34) and then waiting for another (closing) one.

Apparently 8221 is treated as a closing quote.

(or something like that).

That said, you can't use 8220 and 8221 as if they're real quotes.