A related question. I have not followed the header file restructuring discussion. Is there a documentation on header file structure and how they are organized? In a new .c file, simply including gimple.h would require many rounds of iterations to find missing headers via trial (compilation) and error.
thanks, David On Mon, Jan 6, 2014 at 6:16 AM, Andrew MacLeod <amacl...@redhat.com> wrote: > On 12/22/2013 01:27 PM, Jan Hubicka wrote: >> >> >> I believe when the code was created by moving it from elsehwre, the >> copyright should say >> original date of gcov-io.h. >>> >>> + >>> +#include "tconfig.h" >>> +#include "tsystem.h" >>> +#include "coretypes.h" >>> +#include "tm.h" >>> +#include "libgcc_tm.h" >> >> .... >> I would really like someone working on header restructuring to comment on >> those. >> I am not 100% sure what our best practices currently are in respect of >> including headers within headers and specially after good amount of >> defines like gcov-io.h gets included. >> >> > Just back.. > > For the moment the goal with headers is to completely flatten them.. ie, we > do not want to include header files from header files. Once there is a > sensible restructuring of things in place, we are likely to reintroduce them > in a controlled and sensible manner. > > So at the moment, I'd like to not include any additional .h files from > within .h files... > > Andrew > >
