Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1

[Edmund Grimley Evans]

>> he following program is correctly rejected by both GCC and TCC, with
>> fairly similar error messages:
>> int main() { return 0x1e+1; }
>
> Check pcc.
>
>> There should be a space between 0x1e and +1 (see for instance, the
>> output of "gcc -E", "clang -E" and "icc -E")
>
> Space is not required. Check pcc. 0x1e+1 is parsed as 0x1e +1. If
> icc/gcc/clang. complain, then this is theire problem. eE is valid exp
> char only for decimal notation. And for hexadeciamal notation it is an
> ordinal digit char.

Since when has pcc been the official definition of C?

It sounds like pcc has a bug, but I'm not a pcc user and don't intend
to report it.