Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!jarthur!nntp-server.caltech.edu!toddpw
From: toddpw@nntp-server.caltech.edu (Todd P. Whitesel)
Newsgroups: comp.sys.apple2
Subject: Re: ORCA/C Bugs, re typedef structs and/or misplaced globals
Message-ID: <1991Feb26.055721.5142@nntp-server.caltech.edu>
Date: 26 Feb 91 05:57:21 GMT
References: <25642@netcom.COM>
Organization: California Institute of Technology, Pasadena
Lines: 12

Orca seems to be really sensitive about where you put your globals.
Try putting all your globals (except private statics) in the front of
each source file, after the headers but before the first function. I
do this all the time and it works reasonably well.

BEWARE OF USING GLOBAL STRUCTS. I've had the compiler generate totally
bogus code for accessing global structs directly (with .) -- if you auto
the struct or only access the elements through a pointer (as in -> ) then
it works fine.

Todd Whitesel
toddpw @ tybalt.caltech.edu


Brought to you by Super Global Mega Corp .com