🚀 go-pugleaf

In article <9508310634.1386@mulga.cs.mu.OZ.AU>
           fjh@munta.cs.mu.OZ.AU "Fergus Henderson" writes:

> "Brian T. Hill" <bhil@strata3d.com> writes:
> 
> >Who wants to use "true" or "false" in the preprocessor anyway? 
> 
> I do.
> 
> >What are you going to do:  #if true ... ?
> 
> Yes!  Amoung other uses, I'd use `#if true' rather than `#if 1'.
> I don't use `#if 1' very often, but I do use it occaisionally...
> The code ususally looks something like this:
> 
>         #if 1
>                 // alert! this is a temporary hack!!
>                 hack(); hack(); hack();
>         #else
>                 // this code disabled because ...
>                 ...
>         #endif

What's so wrong with saying what you mean:

    #ifndef USE_ORIGINAL_UNHACKED_CODE
        hack(); hack(); hack();
    #else
        // This code disabled because
        ...
    #endif

The point is why change the language to support your idiosyncacies?

-- 
Alan Griffiths               | Also editor of: The ISDF Newsletter
Senior Systems Consultant,   | (An Association of C and C++ Users publication)
CCN Group Limited.           | (ISDF editor  : isdf@octopull.demon.co.uk)
(agriffiths@ma.ccngroup.com) | (For ACCU see : http://bach.cis.temple.edu/accu)
---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]