[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1
From: |
Sergey Korshunoff |
Subject: |
Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1 |
Date: |
Wed, 27 Apr 2016 13:06:14 +0300 |
> 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.
- [Tinycc-devel] parsing 0x1e+1 as 0x1e +1, Sergey Korshunoff, 2016/04/27
- Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1, Vincent Lefevre, 2016/04/27
- Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1, Edmund Grimley Evans, 2016/04/27
- Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1,
Sergey Korshunoff <=
- Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1, Edmund Grimley Evans, 2016/04/27
- Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1, Vincent Lefevre, 2016/04/27
- Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1, Sergey Korshunoff, 2016/04/27
- Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1, Vincent Lefevre, 2016/04/27
- Re: [Tinycc-devel] parsing 0x1e+1 as 0x1e +1, Sergey Korshunoff, 2016/04/27