Path: utzoo!mnetor!uunet!husc6!hao!ames!necntc!ima!haddock!karl
From: karl@haddock.ISC.COM (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: (So-Called) ANSI C
Message-ID: <2046@haddock.ISC.COM>
Date: 21 Dec 87 22:49:31 GMT
References: <4668@pyr.gatech.EDU>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Boston
Lines: 15
Summary: What's broken?

In article <4668@pyr.gatech.EDU> roy@pyr.gatech.EDU (Roy Mongiovi) writes:
>I thought the purpose of X3J11 was to standardize on the existing
>C language.  It seems to me, however, that so many old twists have
>been removed, so many new wrinkles have been added, and so many
>existing C programs broken by the so-called standard that it is
>no longer the same language.

Can you really find a lot of examples of code that will be broken (not just
deprecated) by the new standard?  No fair using code that was already
nonportable under K&R but just happened to work on your compiler.

The only one that springs to my mind is mktemp("fooXXXXXX") (because it's no
longer safe to assume that string literals are writable).

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint