Subject: Re: isprint() and isblank()
To: None <firstname.lastname@example.org>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Date: 01/21/2001 00:53:07
>>> Unfortunately this has the nasty side effect that c will be
>>> evaluated twice, in isblank().
>> which is not permissible by the C standard and would be a cure that
>> kills the patient anyways.
> What in the _world_ are you talking about?!?
while (isblank(*cpp++)) ;
> It's perfectly reasonable to do multiple comparisons/evaluations so
> long as you are not changing the value of the thing being evaluated
> in the process.
Not in a macro whose spec is otherwise.
7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B