[Coco] dbg.l

[Stephen H. Fischer]

Hi,

Check the CoCo Forums post, I stumbled on the actual physical magazine and 
have located the source on a .dsk file which is now attached.

I have included my first "C" Source Archive file which has the Debug Source 
code.

You can ignore or laugh at the rest of the file.

The text of the article is only three pages, I will see if I can scan them 
soon.

Perhaps the code also as it is only 5 pages more. (PC of course, but Pascal 
originally)

-------------------------------------------------------

For extra credit and the answer to my cryptic comment.

Describe the "core" bug in the CoCo OS-9 "C' Library as supplied by Tandy.

SHF

P.S. Send me a text copy or make a post of the header file on the CoCo 
Forums of :

> Actually, the header file for dbg.l is part of the Kreider clib DEFS on
> the old Princeton archive, dbg.h.  It's in "defs.library" wich is a
> uuencoded ar file, originally posted by Pete Lyall.


I may understand what it is doing, I have so large a source of K&R level 
books, CD's and so on.

----- Original Message ----- 
From: "Willard Goosey" <goosey at virgo.sdc.org>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Sunday, May 01, 2011 12:10 AM
Subject: Re: [Coco] dbg.l


> On Sat, Apr 30, 2011 at 09:36:33PM -0700, Stephen H. Fischer wrote:
>
>> I posted the header file which was easy to find on the CoCo Forums.
>> Let me know if this is anything like what you found.
>
> Actually, the header file for dbg.l is part of the Kreider clib DEFS on
> the old Princeton archive, dbg.h.  It's in "defs.library" wich is a
> uuencoded ar file, originally posted by Pete Lyall.
>
> Unfortunately dbg.h not an ansi-ish header that can pass for
> human-readble docs on the library, it just has some constants.
>
>> http://www.tandycoco.com/forum/viewtopic.php?p=368&sid=f8fe7cffd78c9b9e63fede2cb1d53c20#p368
>
> Interesting!  Not the library I'm looking for, but interesting.
>
>> Sorry to those of you stuck in the very far distant past.
>>
> I've done a lot of thinking about that lately, actually.  With the
> exception of people and information disappearing, I'm pretty much right
> where I like to be, programming wise.
>
> Well, OK, it would be nice if the MW C compiler wasn't so utterly
> sex-crazed.  ;-)
>
> Willard