Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!rpi!uupsi!sunic!dkuug!iesd!iesd.auc.dk!richard
From: richard@iesd.auc.dk (Richard Flamsholt S0rensen)
Newsgroups: comp.lang.c
Subject: Re: What the hell does this mean??
Message-ID: <RICHARD.91Mar12035720@euler.iesd.auc.dk>
Date: 12 Mar 91 03:57:20 GMT
References: <6117@mahendo.Jpl.Nasa.Gov>
Sender: news@iesd.auc.dk
Organization: Mathematics and Computer Science, University of Aalborg
Lines: 42
In-reply-to: robert@nereid.jpl.nasa.gov's message of 7 Mar 91 22:43:16 GMT


>>>>> On 7 Mar 91 22:43:16 GMT, Robert Angelino said:
Robert> 		"spa_tclkutc.c", line 130: unacceptable operand of &
Robert> 	on this line
Robert> 		(void) sscanf(ptr,"%04d",&(primary.utc.dy));

  Well, seems as if it very much depends on the type of primary.utc.dy
- only invalid args to & are rvalues, bitfields and registers. You
guys agree with me?

Dave Schaumann:
>[...] comes to mind is that primary was declared as a register variable.

Robert Earl:
>If "dy" is a bitfield member of the struct, [...]

Scott Horne:
>Don't forget bit fields.

Will Crowder:
>This usually indicates trying to take the address of a register variable.

Karl Nicholas:
>If dy is an array, then the address (&) symbol should be omitted.

Checkpoint Technologies:
>Only thing I can think of, is if "dy" is a bit field.

Doug R. Gosciak:
>Is it possible that primary.utc.dy is the name of an array and [...]

  Of course, we *could* ask Robert what type primary.utc.dy has. But
who would ever do that? It would be a total spoiler  ;-)






--
/Richard Flamsholt
richard@iesd.auc.dk