Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!batcomputer!eacj
From: eacj@batcomputer.tn.cornell.edu (Julian Vrieslander)
Newsgroups: comp.sys.mac.programmer
Subject: Don't use Window refCon's when porting to Think C Class Library
Message-ID: <8724@batcomputer.tn.cornell.edu>
Date: 29 Aug 89 03:28:39 GMT
Reply-To: eacj@tcgould.tn.cornell.edu (Julian Vrieslander)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 10
Keywords: WindowRecord refCon Think

Now that we have objects to play with, there is no reason to use the
WindowRecord refCon field for storing data or pointers.  But if you are porting
old code onto the Think C 4.0 Class Library, you can get burned if your routines
write into the refCon.  The Class Library uses this field to store a link to the
owning CWindow object.  I don't think this is mentioned anywhere in the manual.
-- 
Julian Vrieslander 
Neurobiology & Behavior, W250 Mudd Hall, Cornell University, Ithaca NY 14853    
UUCP: {cmcl2,decvax,rochester,uw-beaver}!cornell!batcomputer!eacj
INTERNET: eacj@tcgould.tn.cornell.edu     BITNET: eacj@CRNLTHRY