On 30 sept. 2014, at 23:58, Evan Langlois <[email protected]> wrote:

>> Not exactly:  the C Standard *allows* ? to be escaped as \?, it does not 
>> specify that it should be.
> 
> Hmm .. I stand corrected!  OK - so if it sees \? its ? and if it sees ? it 
> checks to see if its a trigraph, and if it sees \??= then it cries.

To prevent trigraph expansion, the second ? should be escaped.

\??= would trigger the warning "unsupported escape sequence '\#’”  because 
trigraph expansion occurs before escape sequence conversion.

None of this is relevant in tcc, but it is still part of the C standard.
A more recent and less problematic oddity in the C standard syntax is digraphs.
Good news!  tcc does not support digraphs either!

Chqrlie.








_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to