Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!mailrus!ulowell!hawk.ulowell.edu!arosen
From: arosen@hawk.ulowell.edu (MFHorn)
Newsgroups: comp.sys.sequent
Subject: Re: bug in Dynix C compiler.
Message-ID: <11083@swan.ulowell.edu>
Date: 4 Jan 89 20:08:18 GMT
References: <ECLAM.89Jan3081428@maytag.waterloo.edu>
Sender: news@swan.ulowell.edu
Reply-To: arosen@hawk.ulowell.edu
Distribution: comp
Lines: 31

> I found a C compiler bug in the balance C compiler.
> 
>  The following structure definition causes /bin/cc to complain about a
> 
>  struct foo {
>       int private;
>  };
> 
>  The bug is triggered by the keyword "private" inside a structure
>  declaration.  Using "private" outside a structure is fine.
> 
>  The easy solution is to change declarations of "private" to something
>  else. 

In Dynix C, 'private' is a reserved word.  It's used with the parallel
processing libraries.  There is another reserved word called 'shared'.
Their both added variable types.  The above example is thus equivalent

  struct foo {
    int long;
  };

I'm surprised it allows you to use 'private' as a variable name at all,
even outside a structure.  I once tried to use 'auto' as a local variable
name, and it didn't accept that.

--
Andy Rosen           | arosen@hawk.ulowell.edu | "I got this guitar and I
ULowell, Box #3031   | ulowell!arosen          |  learned how to make it
Lowell, Ma 01854     |                         |  talk" -Thunder Road
		RD in '88 - The way it should've been