🚀 go-pugleaf

(question about adding an extension to automatically add trailing
slashes for macro definitions):

| this is very difficult to edit, boring, and often one forget the backslash, ...
| so why not extend the preproc to handle a more complex construct like
| 
| #defmacro foobar(arg_one, arg_two)	{
| 					  if (dummy_function (arg_one)) 
| 					    arg_two = other_dummy (arg_two); 
| 					  else 
| 					    arg_two = arg_one; 
| 					}
| #endmacro

I think this proposed extension should not be added to GCC.  For one
thing, you have people that do things like:

	#define BEGIN {
	#define END }

and such.  I have seen real live exception packages written that have
macros open and close scopes with {}, so it's not just Pascal-dweebs
trying to covert C into their language.  I think that it will break
more code than it's worth.

--
Michael Meissner	email: meissner@osf.org		phone: 617-621-8861
Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142

You are in a twisty little passage of standards, all conflicting.