Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!odi!ed
From: ed@odi.com (Ed Schwalenberg)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Borland C++ bug and impressions
Message-ID: <1991Mar5.144544.22373@odi.com>
Date: 5 Mar 91 14:45:44 GMT
References: <1991Mar4.144002.4355@informix.com>
Organization: Object Design, Inc.
Lines: 18
In-Reply-To: sdavid@infmx.informix.com's message of 4 Mar 91 14:40:02 GMT

In article <1991Mar4.144002.4355@informix.com> sdavid@infmx.informix.com (David Sherrick) writes:

  The first problem I noticed was that Turbo Debugger would not switch from my
  application to the Debugger when I typed ctrl-alt-sysrq.  Borland technical
  support told me that this is a known bug with some systems.  I am using an
  IBM PS/2 Model 70 with an IBM keyboard.

A workaround seems to be to use standard mode.  Too bad for those of us with
386-only code to debug.

  The second thing I noticed (much to my surprise), when I compiled the same
  source code with MSC 6.00 and Borland C++.  The MSC executable was smaller
  than the Borland executable (24k vs 28k) and I had optimization turn OFF 
  in MSC and ON in Borland C++.

Try using TDUMP on both executables and see where the space goes.  Also, both
MSC and BC have multiple optimization switches; reports like this are useless
unless you specify exactly which optimizations were enabled.