home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!src.honeywell.com!The-Star.honeywell.com!umn.edu!csus.edu!netcom.com!netcomsv!terapin!paulk
- From: paulk@terapin.com (Paul Kienitz)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: New hardware reference guide?
- References: <BxyqDB.GCM@cck.coventry.ac.uk>
- Message-ID: <paulk.2asu@terapin.com>
- Date: 20 Nov 92 18:42:14 PST
- Organization: BBS
- Lines: 17
-
- > Er, what is an AutoDoc?
-
- > What i'd like to know is what C= actually object to.
-
- I think I just said something about speaking from ignorance. I
- didn't realize how right I was.
-
- First question: the Autodocs are the official documentation of each
- function in the OS. If you don't read the autodocs then you don't
- know the capabilities of the OS. It really is that simple. Not
- studying the autodocs == not knowing what you're talking about when
- you say what the OS can or can't do.
-
- As for the second question: it's been less than a week since someone
- at C= posted a long and detailed list of exactly which practices are
- the ones that cause programs to mess up on new hardware or new OS
- versions. You could have just gone ahead and read it, you know.
-