Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site utcs.uucp Path: utzoo!utcs!flaps From: flaps@utcs.uucp (Alan J Rosenthal) Newsgroups: net.lang.c Subject: Re: builtins and automatic defines Message-ID: <1243@utcs.uucp> Date: Sat, 17-May-86 02:23:25 EDT Article-I.D.: utcs.1243 Posted: Sat May 17 02:23:25 1986 Date-Received: Sat, 17-May-86 04:27:53 EDT References: <1232@utcs.uucp> <816@bentley.UUCP> Reply-To: flaps@utcs.UUCP (Alan J Rosenthal) Organization: University of Toronto Lines: 29 Summary: In article <816@bentley.UUCP> kwh@bentley.UUCP (KW Heuer) writes: >I wonder if perhaps (and ) should be included by >default, with an explicit "#exclude" to disable. (Cf. "#undef".) Probably >tricky to implement -- don't do the automatic "#include" until checking for >"#exclude", which must be at the top of the file (after whitespace)? Why bother? This would be very complicated and lead to many mistakes due to an unclear definition of whitespace or whatever. I have a file called "beginc", it's a shellscript, and it creates a file which begins something like this: #include #include "/u/flaps/ajr.h" #include #define TRUE 1 #define FALSE 0 main(argc,argv) int argc; char *argv[]; { and then puts you in $EDITOR on the file. This approach is much better than any #exclude op. It's more easily disabled or modified because you don't have the reverse situation of deleting things by adding in lines. -- Alan J Rosenthal {linus|decvax}!utzoo!utcs!flaps, {ihnp4|allegra}!cbosgd!utcs!flaps