Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!mintaka!mintaka.lcs.mit.edu!rearl
From: rearl@churchy.ai.mit.edu (Robert Earl)
Newsgroups: comp.lang.c
Subject: Re: What the hell does this mean??
Message-ID: <REARL.91Mar7212953@churchy.ai.mit.edu>
Date: 8 Mar 91 03:29:53 GMT
References: <6117@mahendo.Jpl.Nasa.Gov> <1083@caslon.cs.arizona.edu>
Sender: daemon@mintaka.lcs.mit.edu (Lucifer Maleficius)
Organization: (EVIL!)
Lines: 23
In-Reply-To: dave@cs.arizona.edu's message of 7 Mar 91 23:37:07 GMT

In article <1083@caslon.cs.arizona.edu> dave@cs.arizona.edu (Dave P. Schaumann) writes:

|   In article <6117@mahendo.Jpl.Nasa.Gov> robert@triton.JPL.NASA.GOV writes:
|   >Hello fellow C programmers,
|   >	I have a small problem:
|   >		"spa_tclkutc.c", line 130: unacceptable operand of &
|   >	on this line
|   >		(void) sscanf(ptr,"%04d",&(primary.utc.dy));
|
|   The first thing that comes to mind is that primary was declared as a
|   register variable.  This is the only circumstance I am aware of that
|   forbids use of the & operator.

If "dy" is a bitfield member of the struct, as in:

      struct foo {
	int dy : 5;
      };

you cannot take its address.


--robert earl