1995-01-27 - Oops, Correction: one big error in “Even more unix holy war.”

Header Data

From: m5@vail.tivoli.com (Mike McNally)
To: cypherpunks@toad.com
Message Hash: 62f0cbbfce8e100d9a5ec0f80ccf6f73bbf06f49acaa26c2edca2700d033f9e2
Message ID: <9501272235.AA05861@vail.tivoli.com>
Reply To: <9501272119.AA00461@carbon.informix.com>
UTC Datetime: 1995-01-27 22:35:59 UTC
Raw Date: Fri, 27 Jan 95 14:35:59 PST

Raw message

From: m5@vail.tivoli.com (Mike McNally)
Date: Fri, 27 Jan 95 14:35:59 PST
To: cypherpunks@toad.com
Subject: Oops, Correction: one big error in "Even more unix holy war."
In-Reply-To: <9501272119.AA00461@carbon.informix.com>
Message-ID: <9501272235.AA05861@vail.tivoli.com>
MIME-Version: 1.0
Content-Type: text/plain



jamesd@com.informix.com writes:
 > This is an error -- what I said was true for C++, but 
 > then in Windows we too are forced to primarily use
 > interpretation to debug C++.   C++ symbolic debuggers
 > are not up to acceptable capabilities in either system.

I hate to contribute to this silliness, but I can't let blatant errors
like this pass.  I debug reams of C++ daily on a wide variety of UNIX
platforms.  With real symbols.  With real C++ expression evaluation an
overload resolution.

(I also get to use compilers that actually come close to supporting
the language as defined by the ARM.)

| GOOD TIME FOR MOVIE - GOING ||| Mike McNally <m5@tivoli.com>       |
| TAKE TWA TO CAIRO.          ||| Tivoli Systems, Austin, TX:        |
|     (actual fortune cookie) ||| "Like A Little Bit of Semi-Heaven" |





Thread