Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!adam.pika.mit.edu!scs
From: scs@adam.pika.mit.edu (Steve Summit)
Newsgroups: comp.lang.c
Subject: Re: Book on Microsoft C
Keywords: Microsoft, C, Version 5, Book
Message-ID: <10107@bloom-beacon.MIT.EDU>
Date: 25 Mar 89 22:16:18 GMT
References: <754@oravax.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: scs@adam.pika.mit.edu (Steve Summit)
Lines: 24

A while ago, someone wrote:

>	I am looking for a good book on Microsoft C (version 5).

Why are there so many books on particular implementations of
languages?  C is supposed to be, and can be, quite portable.
To be sure, there will always be compiler-specific details, which
are the proper province of the compiler user's manuals.  Those
manuals are not always well-written, but they usually tell you
how to invoke the compiler, which ideally is the only compiler-
specific detail you'd need to know.  All of the language
extensions inevitably provided should be avoided whenever
possible, not exploited.

It bugs me to glance into a technical bookstore and see shelf
after shelf of "Programming in Turbo C," "Graphics programming
for the IBM PC," etc.  These books may be the only source of
important documentation, which the irresponsible vendors have
neglected to provide, but they also teach you (if only
implicitly) to write machine-, system-, compiler-, and device-
dependent code.

                                            Steve Summit
                                            scs@adam.pika.mit.edu