🚀 go-pugleaf

	Hey, there -

		someone here just noticed what looks to me like a hole in  
gcc's preprocesor support for Obj-C.  We're trying to implement a macro  
for exception raising - we'd like to do something like :


#define ERROR(errorType, errorString) \
[NSException raise:errorType\
			format:[NSString stringWithFormat:@"%@ at %s :  
%d", \
				errorString, __FILE__, __LINE__]]


	where errorType is one of something like

#define ERRORTYPE1 @"ErrorTypeOne"

	and errorString is an NSString*.  The problem is that sometimes  
I'd like to say

		ERROR(ERRORTYPE1, [NSString stringWithFormat:@"foo : %@",  
[self bar]])

	so I can pass a string generated with printf-style formatting.   
The problem is that the preprocessor chokes with something like :

/CashierPayment.m:209: macro `ISLogError' used with too many (3) args

	apperantly concerned about the two commas, despite the fact that  
one of them is, in reality, part of an expression that should (IMHO) be  
treated as a single macro argument.

	part of my problem may be that I'm using gcc 2.5.8  - does anyone  
know if this problem has been fixed in more recent versions?  (also, as  
may be clear from my examples, I'm on a NeXT).  Am I missing something in  
wanting this feature - i.e., is this not a *bug,* but a necessity for some  
reason?

		Thanks for any help,

				Josh.