[Coco] C Compiler Website / Archive Question

Frank Pittel fwp at deepthought.com
Fri Aug 26 22:17:39 EDT 2011


I have a copy of the original K&R C book somewhere. I'll look for it over
the next few days.

The Other Frank


On Fri, Aug 26, 2011 at 05:55:50PM -0700, Stephen H. Fischer wrote:
> Hi,
> 
> I assume that you are talking about the K&R C book, as I said
> before, only R in in the PDF I found on RTSI.
> 
> Does someone have a printed copy of K&R C book?
> 
> SHF
> 
> 
> ----- Original Message ----- From: "Aaron Wolfe" <aawolfe at gmail.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Friday, August 26, 2011 5:44 PM
> Subject: Re: [Coco] C Compiler Website / Archive Question
> 
> 
> I noticed the C Compiler manual on cococoding.com was not yet OCR'ed.
> I ran it through the usual process and replaced the file previously
> there with the updated version.  It did a decent job, for instance,
> page 1 copied and pasted:
> 
> 
> The ncn programming language is rapidly growing in popularity
> and seems destined to become one of the most popular programming
> languages used for microcomputers. The rapid rise in the use of C
> is not surprising. C is an incredibly versatile and efficient
> language that can handle tasks that previously would have required
> complex assembly language programming.
> 
> C was originally developed at Bell Telephone Laboratories as an
> implementation language for the UNIX operating system by Brian
> Kernighan and Dennis Ritchie. They also wrote a book titled "The C
> Programming Language" which is universally accepted as the standard
> for the language. It is an interesting reflection on the language
> that although no formal industry-wide "standard" was ever developed
> for C, programs written in c tend to be far more portable between
> radically different computer system as compared to so-called
> "standardized" languages such as BASIC, COBOL, and PASCAL. The
> reason C is so portable is that the language is so inherently
> expandable that if some special function is required, the user can
> create a portable extension to the language, as opposed to the
> common practice of adding additional statements to the language.
> For example, the number of special-purpose BASIC dialects defies all
> reason. A lesser factor is the underlying UNIX operating system,
> which is also sufficiently versatile to discourage
> nonstandardization of the language. Indeed, standard C compilers
> and Unix are intimately related.
> 
> Fortunately, the 6809 microprocessor, the OS-9 operating
> system, and the C language form an outstanding combination. The
> 6809 was specifically designed to efficiently run high-level
> languages, and its stack-oriented instruction set and versatile
> repertoire of addressing modes handle the C language very well. As
> mentioned previously, UNIX and C are closely related, and because
> OS-9 is derived from UNIX, it also supports C to the degree that
> almost any application written in C can be transported from a UNIX
> system to an OS-9 system, recompiled, and correctly executed.
> 
> 
> If thats of use to you, enjoy and distribute any way you like, as far
> as I am concerned :)
> 
> 
> 
> 
> 
> On Fri, Aug 26, 2011 at 8:28 PM, Stephen H. Fischer
> <SFischer1 at mindspring.com> wrote:
> >Hi,
> >
> >Both of the two manuals I list appear to be clean perfect copies.
> >
> >The one from NitrOS-9 may have started from a very poor scan I did decades
> >ago but a huge amount of manual editing I believe has been done to produce
> >what I converted to PDF.
> >
> >Someone needs to step up and tell me how to give credit for some of the
> >stuff I am assembling.
> >
> >I have not started to compare the NitrOS-9 C Compiler with my printed
> >version but I expect them to match.
> >
> >I am unsure if I have a printed copy of K&R's C book. What I found
> >on RTSI I
> >would not expect to match.
> >
> >If you are interested, please compare your printed books with the files.
> >
> >http://www.tandycoco.com/forum/viewtopic.php?p=533#p533
> >
> >>>Is there a version of the K&R book online which can be
> >>>included in the "C
> >>>Compiler Documentation Disk?
> >>>
> >>
> >>
> >>Aaron has a copy of this document on CocoCoding:
> >
> >I will check his site and if it is good add it to the C Compiler
> >Documentation disk.
> >
> >Thanks for the help, it is looking like this project is much larger than I
> >planned to do so any help is very good.
> >
> >SHF
> >
> >----- Original Message ----- From: "Michael Furman" <n6il at ocs.net>
> >To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> >Sent: Friday, August 26, 2011 4:57 PM
> >Subject: Re: [Coco] C Compiler Website / Archive Question
> >
> >
> >>
> >>On Aug 26, 2011, at 3:10 PM, Stephen H. Fischer wrote:
> >>
> >>>Hi,
> >>>
> >>>I have successfully converted the "C_Compiler_User_Guide" to PDF from:
> >>>
> >>>
> >>>http://sourceforge.net/apps/mediawiki/nitros9/index.php?title=C_Compiler_User%27s_Guide
> >>>
> >>>This was done in preparation of building the "C Compiler Documentation
> >>>Disk".
> >>>
> >>>Should I have done so?
> >>
> >>
> >>MaltedMedia has a scan of the original manual.
> >>
> >>
> >>ftp://ftp.maltedmedia.org/coco/MANUALS/TANDY/SOFTWARE/TANDY_OS9/OS9%20C%20Compiler.7z
> >>
> >>I prefer to not have to deal with any OCR errors that typically occur in
> >>translation. One particularly bad example is the user manual for the
> >>Sinclair QL. It's almost unusable. I don't really see value in a PDF
> >>version of a Wiki Page -- The original typesetting and formatting is gone
> >>and I can read the Wiki page any time with any web browser if I
> >>choose to by
> >>clicking on your link.
> >>
> >>Aaron also has this on CocoCoding. Aaron's version is using ClearScan OCR
> >>or similar to reduce the file size, so you only see the OCR errors if you
> >>cut and paste the text:
> >>
> >>
> >>https://sites.google.com/a/aaronwolfe.com/cococoding/home/docs/CCompilerUser%27sGuide-Microware%281983%29.pdf?attredirects=0&d=1
> >>
> >>
> >>
> >>>
> >>>------------------------------
> >>>
> >>>I also found perhaps the initial version of K&R's C language book in a
> >>>file on RTSI, but the author is given as:
> >>>
> >>>
> >>>
> >>>Dennis M. Ritchie
> >>>Bell Telephone Laboratories
> >>>Murray Hill, New Jersey 07974
> >>>
> >>>
> >>>
> >>>Nothing is said about Brian Kernighan.
> >>>
> >>>
> >>>
> >>>Is there a version of the K&R book online which can be
> >>>included in the "C
> >>>Compiler Documentation Disk?
> >>>
> >>
> >>
> >>Aaron has a copy of this document on CocoCoding:
> >>
> >>
> >>https://sites.google.com/a/aaronwolfe.com/cococoding/home/docs/TheCProgrammingLanguage.pdf?attredirects=0&d=1
> >>
> >>I found a scan of the book version somewhere, but don't have a reference
> >>to it handy.
> >>
> >
> >
> >--
> >Coco mailing list
> >Coco at maltedmedia.com
> >http://five.pairlist.net/mailman/listinfo/coco
> >
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



More information about the Coco mailing list