Path: utzoo!attcan!uunet!decwrl!sun-barr!cs.utexas.edu!mailrus!iuvax!ux1.cso.uiuc.edu!midway!magrathea!francis
From: francis@magrathea.uchicago.edu (Francis Stracke)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think C Objects in motion???
Message-ID: <1990Sep25.160926.14926@midway.uchicago.edu>
Date: 25 Sep 90 16:09:26 GMT
References: <1990Sep14.105646.23614@cunixf.cc.columbia.edu>
Sender: news@midway.uchicago.edu (News Administrator)
Organization: Mathematics Department, University of Chicago
Lines: 17

In article <1990Sep14.105646.23614@cunixf.cc.columbia.edu> wlj1@cunixb.cc.columbia.edu (Wayne L Jebian) writes:
>
>I've noticed some strange behavior from the TCL.
>
>Sometimes when I execute a toolbox call from within a method, I get the 
>ubiquitous odd address error. This had me _REALLY CONFUSED_ until I
>tried putting the offending calls in other places: that is,
>in glue that put the trap calls outside the object's struct.
>
>Well, now my code doesn't break but I'm still confused. Is code (the methods)
>being moved around without updating the PC? I thought that the objects could
>be treated transparently as pointers - i.e. no locking required.

I do know that Think Pascal uses handles instead of pointers to reference the
objects--but only their data should be in the block referenced.  The code
should be in the CODE resources like any other.  The object's block of RAM
just holds pointers (or something) to tell what routines to call.