Path: utzoo!utgpu!cunews!cognos!rossj
From: rossj@cognos.UUCP (Ross Judson)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Mark Williams C funnies
Message-ID: <9234@cognos.UUCP>
Date: 22 Jan 91 07:10:08 GMT
References: <9224@cognos.UUCP> <1991Jan18.225523.22934@daffy.cs.wisc.edu>
Reply-To: rossj@cognos.UUCP (Ross Judson)
Organization: Cognos Inc., Ottawa, Canada
Lines: 27

In article <1991Jan18.225523.22934@daffy.cs.wisc.edu> gcarter@gumby.cs.wisc.edu (Gregory Carter) writes:
>MWC's CSD is flaky as all hell.  I am surprised your actually trying to use
>that thing.  If your doing something that complex, that you need a source
>debugger, I would trash MWC and get Borlands package.
>THERE are a LOT of strange things that compiler system does for the ST,
>if you don't at least have version 3.0.6 I really question whether its
>useful for anything but light and medium-light jobs.

These are fairly strong statements.  It would be great if you could
provide a few concrete examples of problems.

There are several problems with switching compilers.  The main one is
that my program is uses a lot of the MWC specific features in the
library.  These would all have to be converted to a new compiler.
Second, it costs to buy a new compiler.  I already have one and I'm
very satisfied with it, except for the debugging strangeness.

But I'm curious.  Where can one get the Borland C package in Canada?

Is anyone aware of a profiler that is compatible with MWC version 3
binaries?  Some time ago (1987) David Rowley released a profiler for
MWC v2 and alcyon/dri format executables.  Has this ever been updated
for v3 executables?

-- 
Ross Judson ++ uunet!mitel!cunews!cognos!rossj + hunger is the fuel of greed
Cognos Inc. ++ rossj@cognos.uucp               + enough is less than you need