[Coco] OS-9 C Compiler

[Stephen H. Fischer]

> Probably not as that kind of integration is generally not the UNIX way. 

Ah, the root of the deficiency has been found. Don't ever do anything that would be useful as the years go by.

> external debugger on your code.  There are things like eclipse which 
> will call all of these programs for you and make them appear integrated.

Setting breakpoints at the "C" source level?

When you hit a breakpoint can you then look at your variables in their natural form.

Single step one "C" line at a time?

define "watches" so that you can see their variables as they change in real time?

And more debugging options at the "C" source level? 

----------------------------------
What about Java?

SHF
----- Original Message ----- 
From: "Theodore (Alex) Evans" <alxevans at concentric.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Tuesday, February 16, 2016 5:58 PM
Subject: Re: [Coco] OS-9 C Compiler


> On 02/16/2016 06:20 PM, Stephen H. Fischer wrote:
> 
>> Does gcc6809 have a IDE = Integrated *DEBUGGING" Environment? That is with source level debugging which Borland hooked me with immediately.
> 
> Probably not as that kind of integration is generally not the UNIX way. 
>  The most common thing to use with gcc is to pass -g then use an 
> external debugger on your code.  There are things like eclipse which 
> will call all of these programs for you and make them appear integrated.
>