Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!news.cs.indiana.edu!ariel.unm.edu!triton.unm.edu!saunders
From: saunders@triton.unm.edu (Richard Saunders CIRT)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Information on Amiga Technical Reference Seri
Message-ID: <1991Jun07.214314.5832@ariel.unm.edu>
Date: 7 Jun 91 21:43:14 GMT
References: <1057.284e0dbf@vger.nsu.edu> <91158.110654GHGAQA4@cc1.kuleuven.ac.be> <22247@cbmvax.commodore.com>
Organization: University of New Mexico, Albuquerque
Lines: 29

In article <22247@cbmvax.commodore.com> ken@cbmvax.commodore.com (Ken Farinsky - CATS) writes:
>In article <91158.110654GHGAQA4@cc1.kuleuven.ac.be> GHGAQA4@cc1.kuleuven.ac.be (Tyberghein Jorrit) writes:
>>>I am glad that you put a smiley on the end.  The last thing we need is
>>>apublic domain version of the kernal.  In fact, I am against Commodore
>>>releasing the SOURCE CODE to the operating system.  That would be a
>>>complete disaster.
>>
>>Please explain what is so bad about releasing the source code ? I
>>don't see your point.
I agree.
>
>Don't worry, Commodore will never release the source code.  We'll do
>our best to document it, though.  Let's concentrate on making killer
>applications!
>-- 
>Ken Farinsky - CATS - Commodore Business Machines
That's too bad ... having the source code around for your operating
system is extremely useful ... it's instructive (you can see how the
"pros" did it), allows you to fix bugs you find immediately,
(this is the reason Matt Dillon included the source for his Library
 in DICE), and is, in a sense, the ultimate documentation for the
operating system (manuals always tend to be incomplete/out of date).

IMHO, I think it would be nice to have the source for everything I ever
used.  Why? I like to know how things are done ...

Oh well. It's a moot point anyway. 

* saunders@triton.unm.edu * "This is _NOT_ Mel Torme!" - Top Secret