Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!sdd.hp.com!wuarchive!uunet!keinstr!chaplin
From: chaplin@keinstr.uucp (chaplin)
Newsgroups: comp.lang.c
Subject: Re: C language book recommendations
Message-ID: <1991Jun4.212317.1213@keinstr.uucp>
Date: 4 Jun 91 21:23:17 GMT
References: <36770001@hpopd.pwd.hp.com> <1991May21.125840.12654@ccu.umanitoba.ca> <741@taumet.com>
Organization: Keithley Instruments, Cleveland, Ohio
Lines: 21

In article <741@taumet.com> steve@taumet.com (Stephen Clamage) writes:
>Look over the material again.  In their book, H&S are not presenting only
>ANSI C.  They are trying to cover the range of C implementations which have
>been at all widely used.  If you have to write code for a variety of C
>implementations, or understand some moldy old code written for some
>system you do not have access to, this book will help.  It explains all
>the common things which have been done, and how you can get your code
>to work.

>Steve Clamage, TauMetric Corp, steve@taumet.com

I have the 2nd Edition, which has a separate chapter dealing with "draft
proposed ANSI C".  I personally prefer this approach, exactly for the
reason you mention: not all the compilers I use are ANSI.  Perhaps the
other changes in the 3rd Edition (I assume there are some) would make
it worthwhile to have.
-- 
Roger Chaplin / Instruments Division Engineering | "There are two types of
chaplin@keinstr.uucp / CI$: 76307,3506           | people: those who divide
#include <disclaimer.h>                          | people into two types, and
#include "disclaimer.h"  /* cover all bases */   | those who don't." - Barth