• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Re(2): CriticalAlert
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re(2): CriticalAlert


  • Subject: Re: Re(2): CriticalAlert
  • From: "John C. Randolph" <email@hidden>
  • Date: Thu, 20 Dec 2001 23:09:48 -0800

On Thursday, December 20, 2001, at 09:08 PM, Vince DeMarco 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
> later. If i had to edit code like that the first thing i would
> do is switch everything back to normal and remove the macros.

Funny, I've used global search and replace to find instances of
assignments that should be comparisons!

I first mentioned this on comp.lang.c sometime in the mid-80's,
and I got a *lot* of responses, from "That's a great idea, I'll
do it from now on", to "You're trying to abuse the preprocessor
to make C into COBOL!"

-jcr


"The problem with trying to child-proof the world, is that it
makes people neglect the far more important task of
world-proofing the child." -- Hugh Daniel


References: 
 >Re: Re(2): CriticalAlert (From: Vince DeMarco <email@hidden>)

  • Prev by Date: DO, NSConnection, NSThreads, NSRunLoops, and method running/stopping
  • Next by Date: Re: Silly question
  • Previous by thread: Re: Re(2): CriticalAlert
  • Next by thread: Re(4): CriticalAlert
  • Index(es):
    • Date
    • Thread