Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site cybvax0.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!harvard!wjh12!genrad!mit-eddie!cybvax0!aug From: aug@cybvax0.UUCP (Amit Green) Newsgroups: net.lang.c Subject: Re: Fuel for your flames: Things I would like in CPP Message-ID: <163@cybvax0.UUCP> Date: Sun, 7-Oct-84 16:59:09 EDT Article-I.D.: cybvax0.163 Posted: Sun Oct 7 16:59:09 1984 Date-Received: Tue, 9-Oct-84 19:43:19 EDT References: <9225@watmath.UUCP> <4092@tekecs.UUCP> Organization: Cybermation, Inc., Cambridge, MA Lines: 24 >Kevin Martin writes <9225@watmath.UUCP>: > 4) Given proper macros, it is now useful to have the ability to > issue error messages, perhaps including a severity (warning -- > the compile can continue, error -- CPP can continue, but the compiler > should not be called up, fatal -- force CPP to give up immediately). > #message 0 "Warning: NUM < 0" > Maybe the quotes aren't needed... I think this would be usefull. Currently I have to use something like this: #ifndef BUFSIZ # include "? Whoops - BUFSIZ not defined" #endif >joemu@tekecs writes <4092@tekecs.UUCP> > Should benign (identical) redefinition of a macro be allowed? I think this would be usefull; and harmless. I often redefine routines (in different include files of course): extern char *retstring () ; extern char *retstring () ; If I sometimes changed retchar to a macro, I would want to be able to have the following in both my include files also: #define retstring(s) "s"