Re(4): CriticalAlert
Re(4): CriticalAlert
- Subject: Re(4): CriticalAlert
- From: Jens Bauer <email@hidden>
- Date: Fri, 21 Dec 2001 09:44:24 +0100
Hi Vince,
On Thu, 20 Dec, 2001, Vince DeMarco <email@hidden> wrote:
>
>
On Thursday, December 20, 2001, at 11:58 am, Jens Bauer wrote:
>
>
> Hi John,
>
>
>
>
>
>> #define is ==
>
>> #define or ||
>
>> #define and &&
>
>
>
> Definately a good solution!
>
>
>
>
Except for the poor developer who has to maintain your code latter. If i
>
had to edit code like that the first thing i would do is switch everything
>
back to normal and remove the macros.
I agree; if you're many developers, I would not recommend it in code that is
shared with others. But for the initial work, it would be a good idea, and
to find out where you placed all the "is" macros, you could do a
#define is <<<changeme>>>
Then re-compile, change them back, and ship the code. :)
-But GCC *is* a good compiler, so you won't need that if you keep your code
clean of warnings.
Love,
Jens