Path: utzoo!attcan!uunet!lll-winken!ames!ucsd!rutgers!cs.utexas.edu!utastro!james
From: james@utastro.UUCP (James McCartney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: serious code generation bug in Lightspeed C
Message-ID: <3529@utastro.UUCP>
Date: 12 Jan 89 18:39:56 GMT
References: <6275@hoptoad.uucp>
Organization: U. Texas, Astronomy, Austin, TX
Lines: 11

In article <6275@hoptoad.uucp>, tim@hoptoad.uucp (Tim Maroney) writes:
> There is a serious bug in how Lightspeed C handles the assignment
> operation.  The lvalue is evaluated before the value is computed.  This
> means that assigments to relocatable structure members do not work
> correctly.

   Whether or not it is a bug, it used to be documented in the Xeroxed
supplement to the Lightspeed C manual. It doesn't seem to be in the new 
manual. I got bit by this one too long ago. Another workaround is to
lock and unlock the handle if you have several of these type of assignments.
   --- James McCartney