[futurebasic] Re: Weird Global Behavior (TCP)

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : May 1998 : Group Archive : Group : All Groups

From: Greg_Neagle@...
Date: Sat, 30 May 1998 11:00:04 -0700
On 5/30/98 at 8:52 AM, Brian Victor wrote:

:I can't figure out why that variable is changing, though.  It's declared in
:TCP-DNR.GLBL, which is included in a GLOBALS statement in both my main
:program and TCP-DNR.INCL.  The COMPILE line is exactly the same in my main
:file and the include file.  The code below is everything I have before the
:local functions in my main program:
:
:
:COMPILE
:0,_dimmedVarsOnly_noRedimVars_macsBugLabels_caseInsensitive_STRresource
:
:GLOBALS "BoardDraw.glbl"
:GLOBALS "lineconsole.glbl"
:GLOBALS "chessprefs.glbl"
:GLOBALS "menus.glbl"
:GLOBALS "TCP-DNR.GLBL"
:GLOBALS "myTCP.glbl"
:REM input is coming from server, output is going to server
:DIM gInputBuffer$,gOutputBuffer$
:'DIM gTCPHostName$,gTCPport,gTimeOutTicks&,gConnected
:END GLOBALS

Does your TCP-DNR.INCL begin with this EXACT same sequence?  If not, the
TCP-DNR.INCL thinks the globals it needs are in a different memory space than
the main does.  In other words, the Main thinks the TCP globals are stored in
memory AFTER the BroadDraw, lineconsole, chessprefs and menus globals.  The
TCP-DNR.INCL must have the same information available to it.



- BulkRate: the FirstClass offline reader for Macintosh