🚀 go-pugleaf

Pieter Hintjens (pahint@eunet.be) wrote:
[snip]
: When I started with this 'universal header file' the motivation was
: to let me edit and compile my code on a PC, with Borland's fast tools
: and their pop-up help.  Once I had a 'clean' source I could recompile
: and test on the UNIX.

: This still stands.  On my cheap pentium, Turbo-C is *fast*.  Even
: with all the include's.  The total time I spend compiling is much
: less than if I worked only on a UNIX, with a many fewer include's.

: Sure, I can't really test my code, but I tyep baldy^H^H^H^H^H^Htype
: badly, and I save a lot of time by editing and proof-compiling on
: the platform of choice.

: Okay, point taken about including masses of files: I am making the
: UIF smarter, so that you can tune it with a few #define's at the
: start of your program.

: Anyone interested in following this project, drop me a line. 
: --
: Pieter A. Hintjens

With almost any well thought-out project, there's usually an associated
rationale (take the C Standard for instance).  However, I really don't
see any point in creating a "universal header file".  It's like the
physics profs drill into our heads "you can't get something for nothing".
Kind of a conservation of CPU cycles principle :)

Anyway... if you want to do something useful, write a piece of code that
scans C source modules and determines what headers should be included and
add those to the source.  Otherwise, you'll end up with a bunch of useless
clutter with .h as its file extension.  (However, such a product might
get you hired by Microsoft :)

Greg
--
Greg Bacon <gbacon@cs.uah.edu>
University of Alabama in Huntsville
CS Department Systems Support Team