Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Quote mangling in TCC

Charles Dye

Super Moderator
May
4,997
129
Staff member
What's going on here?

Code:
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?
 
I wonder if TCC is treating the first one as a real (opening) double quote (34) and then waiting for another (closing) one.

1673030041663.png


Apparently 8221 is treated as a closing quote.

1673030212888.png


(or something like that).

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

1673030537537.png
 

Similar threads

Back
Top