Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cadnetix.COM!cadnetix!pem
From: pem@cadnetix.COM (Paul Meyer)
Newsgroups: comp.sys.mac.programmer
Subject: Re: TransSkel [sic] problems with LSC v3?
Message-ID: <8056@cadnetix.COM>
Date: 23 May 89 16:10:49 GMT
References: <301@indri.primate.wisc.edu>
Sender: news@cadnetix.COM
Reply-To: pem@cadnetix.COM (Paul Meyer)
Organization: Cadnetix Corp.,  Boulder, CO
Lines: 25

In article <301@indri.primate.wisc.edu> bin@primate.wisc.edu (Brain in
Neutral) writes for Barry Kirsch:
>>"upgraded" to version 3 of Think C, and my programs are not running
>>smoothly (or at all some times) (Crashes and mouse freezes).
	I've not had this problem at all.  Do you have the latest
patches (3.01p4 or 3.02)?

>>The first problem, it would not compile when I called CtoPstr(str)
>>when str was defined as Str255  str.  I changed it to char *str, to
	I tend to never use Str255, since to me that implies char [256], and
both in usage and in the include files it is really char *.  Perhaps this
is your problem--did Str255 change, Rich?
	In the rare cases where "Str255" is actually used in a prototype,
I cast my "char *" (or "char []") at the call so I still know what I'm doing.

>>match the prototype.  Other problems that I can't easily isolate have to
>>do with the ProcPtr's in the SkelWindow calls.
	I have had no problems with this at all.  I write my routines, I
forward-declare them and pass them with ProcPtr casts.  No problem.  Perhaps
ProcPtr is normally a pascal routine and that's the problem?

Paul Meyer                      pem@cadnetix.COM
Cadnetix Corp.			{uunet,boulder}!cadnetix!pem
5775 Flatirons Pkwy.            GEnie P.MEYER
Boulder, CO 80301               (303)444-8075x277