Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!rex!rouge!ralph!elgamy!elg From: elg@elgamy.raidernet.com (Eric Lee Green) Newsgroups: comp.sys.amiga.programmer Subject: Re: Information on Amiga Technical Reference Seri Message-ID: <00677916042@elgamy.raidernet.com> Date: 26 Jun 91 05:00:42 GMT References: <3036@public.BTR.COM> <22455@cbmvax.commodore.com> <22523@cbmvax.commodore.com> Organization: Eric's Amiga 2000 @ Home Lines: 23 From article , by mykes@amiga0.SF-Bay.ORG (Mike Schwartz): > Hey, if I could step through beta OS routines with CPR or SDB with FULL source, > I would be able to give you REAL accurate bug reports. I could tell you what file > had the bug, what the problem is, and what to change to fix the problem. > Make it all available in machine readable form. Just make sure it all makes... Hah! CPR would blow up (debug stuff is too gruesome), and I don't know if you have enough hard drive space for the full source anyhow :-). (It's all done using a huge NFS partition on their VAX). Not to mention that some of the tools they use don't even run on the Amiga (like GreenHills "C", which a few parts of the OS are still written in). > Put all the disclaimers you want on the source code. Why not put the RKM in machine > readable form, too? There are a lot of program fragments that would be nice to be > able to cut and paste from. An on-line manual with documented source could be put The RKM source code available on the Fish disks and on BIX. I have it sitting on my DH1: partition. Comes in handy, for snipping parts of their console-handling code etc... -- Eric Lee Green (318) 984-1820 P.O. Box 92191 Lafayette, LA 70509 elg@elgamy.RAIDERNET.COM uunet!mjbtn!raider!elgamy!elg