Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp
Path: utzoo!linus!philabs!prls!amdimage!amdcad!decwrl!sun!guy
From: guy@sun.uucp (Guy Harris)
Newsgroups: net.unix,net.bugs.4bsd
Subject: Re: Compiler bug
Message-ID: <2192@sun.uucp>
Date: Sat, 18-May-85 03:52:06 EDT
Article-I.D.: sun.2192
Posted: Sat May 18 03:52:06 1985
Date-Received: Mon, 20-May-85 04:23:25 EDT
References: <1136@sjuvax.UUCP> <136@drivax.UUCP>
Distribution: net
Organization: Sun Microsystems, Inc.
Lines: 20
Xref: linus net.unix:3980 net.bugs.4bsd:1229

> > extern int usr1(), usr2(), usr3();
> > 
> > int	usrprocs[] = { usr1, usr2, usr3 }
> > 
> > Would someone be good enough to check this out on a sysV machine?
> 
> My SysV machine (VAX) gives me:
> "bug.c", line 3: warning: illegal combination of pointer and integer, op =
> "bug.c", line 3: warning: illegal combination of pointer and integer, op =
> "bug.c", line 3: warning: illegal combination of pointer and integer, op =
> 
> This is what I would expect. What did BSD do?

The same thing (although my 4.2BSD machine is a Sun, I think it does the
same thing on a VAX; the 4.2BSD VAX compiler is basically the SysIII
compiler).  *Everybody* should expect it.  The above code is simply wrong.
If your compiler doesn't complain, complain to the author(s) of your
compiler.  "Type-correctness is everybody's business."

	Guy Harris