[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] #include_next troubles
From: |
Edmund Grimley Evans |
Subject: |
Re: [Tinycc-devel] #include_next troubles |
Date: |
Tue, 20 Oct 2015 15:49:47 +0100 |
> I don't found by Google any description about how #include_next must
> behave.
It's a non-standard GCC extension. You should start off by thoroughly
investigating how GCC handles it. Don't trust the documentation. Make
a small test suite and try both an ancient and a modern version of
GCC.
You could refer to GCC's source and test suite but it might be more
productive to take a fresh look at it. GCC's source might be hard to
understand, and GCC's test suite might be incomplete.
Edmund
- Re: [Tinycc-devel] #include_next troubles, Sergey Korshunoff, 2015/10/17
- Re: [Tinycc-devel] #include_next troubles, Assaf Gordon, 2015/10/18
- Re: [Tinycc-devel] #include_next troubles, Sergey Korshunoff, 2015/10/19
- Re: [Tinycc-devel] #include_next troubles, Sergey Korshunoff, 2015/10/20
- Re: [Tinycc-devel] #include_next troubles, Sergey Korshunoff, 2015/10/20
- Re: [Tinycc-devel] #include_next troubles, grischka, 2015/10/20
- Re: [Tinycc-devel] #include_next troubles, Sergey Korshunoff, 2015/10/20
- Re: [Tinycc-devel] #include_next troubles,
Edmund Grimley Evans <=
- Re: [Tinycc-devel] #include_next troubles, Sergey Korshunoff, 2015/10/20
- Re: [Tinycc-devel] #include_next troubles, grischka, 2015/10/20
- Re: [Tinycc-devel] #include_next troubles, Edmund Grimley Evans, 2015/10/21
- Re: [Tinycc-devel] #include_next troubles, Sergey Korshunoff, 2015/10/21
- Re: [Tinycc-devel] #include_next troubles, Sergey Korshunoff, 2015/10/22