rex@aussie.COM (Rex Jaeschke) (03/21/91)
Re the posting from vinoski@apollo.hp.com, Sam Harbison replies:
Stephen,
Your message on comp.lang.c regarding C:A Reference Manual (3/e) was
forwarded to me. I looked at the example you mentioned (p. 287), and
it is indeed incorrect. Sorry. Here's a correction, in the style of the
current example:
#include <string.h>
char *strcat(dest,src)
char *dest;
const char *src;
{
char *s = dest + strlen(dest); /* changed */
strcpy(s, src); /* changed */
return dest;
}
As for the other typos you mentioned, please send me a list of what
you found and I will have the problems fixed in the next printing.
Like software bugs, book bugs only get fixed when they get reported.
My list of "known bugs" with the 3rd edition was empty until I saw
your mail.
Thanks,
Sam Harbison
Pine Creek Software
305 S. Craig St., Suite 300
Pittsburgh, PA 15213
+1 412 681 9811
harbison@bert.pinecreek.com
Rex
----------------------------------------------------------------------------
Rex Jaeschke | Journal of C Language Translation | C Users Journal
(703) 860-0091 | 2051 Swans Neck Way | DEC PROFESSIONAL
rex@aussie.COM | Reston, Virginia 22091, USA | Programmers Journal
----------------------------------------------------------------------------
Convener of the Numerical C Extensions Group (NCEG)
X3J11 member and US International Representative to ISO C (WG14)
----------------------------------------------------------------------------diamond@jit345.swstokyo.dec.com (Norman Diamond) (03/22/91)
In article <62.UUL1.3#5077@aussie.COM> rex@aussie.COM (Rex Jaeschke) posts Sam Harbison's reply: >Like software bugs, book bugs only get fixed when they get reported. Sorry Mr. Harbison, but many book bugs could be fixed by testing. This fact was known even before your 1st edition, because the problem is so widespread. Followups to comp.misc. -- Norman Diamond diamond@tkov50.enet.dec.com If this were the company's opinion, I wouldn't be allowed to post it.