Reducing the header maze (warning: long, unsuitable for children)

2002-12-03 Thread Greg Turner
I'm working on Ove's comhdr1 comhdr2 patches. So far, so good, btw -- I have it compiling against yesterday's CVS (recent commits are not folded in yet). I'll submit after I kick the tires a bit and make sure everything seems to be working (otherwise, I'll probably post it here and ask for

Re: Reducing the header maze (warning: long, unsuitable for children)

2002-12-03 Thread Alexandre Julliard
Greg Turner [EMAIL PROTECTED] writes: This should ensure that each header can actually be run through the compiler all by itself -- that is, that it #include's any headers it relies on to compile. We don't want that, it's not what Windows does. But yes, the whole obj_*.h stuff is a mess,

Re: Reducing the header maze (warning: long, unsuitable for children)

2002-12-03 Thread Joerg Mayer
Now, here's my question: couldn't we build a script to automatically fix some of these problems? Imagine this pseudocode as a bash script, makefile, or something along those lines: o gather and create a table of all .c - .h and .h - .h dependencies o for each file: o one by one, try

Re: Reducing the header maze (warning: long, unsuitable for children)

2002-12-03 Thread Francois Gouget
On Tue, 3 Dec 2002, Greg Turner wrote: [...] Anyhow, this project has served to remind me just how deep, and how confusing, the maze of wine headers can really be. It's clear to me that lots of header inclusions are just historical remnants, that no longer serve any purpose, and, conversely,

Re: Reducing the header maze (warning: long, unsuitable for children)

2002-12-03 Thread Greg Turner
On Tuesday 03 December 2002 04:07 pm, Alexandre Julliard wrote: Greg Turner [EMAIL PROTECTED] writes: This should ensure that each header can actually be run through the compiler all by itself -- that is, that it #include's any headers it relies on to compile. We don't want that, it's not