From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <775b8d19050526100248e33f1d@mail.gmail.com>
Date: Fri, 27 May 2005 03:02:19 +1000
From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 8c funny
In-Reply-To: <70a42a4d7b217162f91a2824c4795fe7@coraid.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <70a42a4d7b217162f91a2824c4795fe7@coraid.com>
Topicbox-Message-UUID: 557a0e94-ead0-11e9-9d60-3106f5b1d025

yes, it's "only one prize per child".  if cc finds an error (or warning)
in an expression it generally bails on that item - avoiding the
"cascade of errors" from a simple typo.  sometimes it can be
annoying (fix "b" in this case and next compile it will complain
about "a") but usually it saves investigating non-errors.

brucee

On 5/27/05, Brantley Coile <brantley@coraid.com> wrote:
> Any one seen this before?
>=20
> term% cat busted.c
> #include <u.h>
> #include <libc.h>
>=20
> void
> main(void)
> {
>        vlong a;
>        int b;
>=20
>        if (a =3D=3D b)
>                exits(nil);
>        exits(nil);
> }
> term% 8c -FVw busted.c
> warning: busted.c:5 used and not set: b
> term%
>=20
> Note that a doesn't get tagged as used and not set.
>=20
>=20
>  Brantley