Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!uniwa!vaxa.cc.uwa.oz.au!n_hays
From: n_hays@vaxa.cc.uwa.oz.au
Newsgroups: comp.sys.mac.programmer
Subject: Re: Weird Think C problems
Message-ID: <1990Aug14.003350.2055@vaxa.cc.uwa.oz.au>
Date: 13 Aug 90 16:33:50 GMT
Organization: University of Western Australia
Lines: 46




>From:	SMTP%"jackiw@cs.swarthmore.edu"
>To:	n_hays@vaxa.cc.uwa.oz.au
>?CC:	
>Subj:	Re: Weird THINK C problems

>Date: Mon, 13 Aug 90 11:30:21 EDT
>From: jackiw@cs.swarthmore.edu (Nick Jack: <9008131530.AA02707@swatsun.cs.swarthmore.edu>
>To: n_hays@vaxa.cc.uwa.oz.au
>Subject: Re: Weird THINK C problems
>Newsgroups: comp.sys.mac.programmer,aus.mac
>In-Reply-To: <1990Aug11.225521.2051@vaxa.cc.uwa.oz.au>
>References: <11088@wehi.dn.mu.oz>
>Organization: Visual Geometry Project, Swarthmore College, PA

>Can you send a page reference to this warning about SuperClock in
>the manual?  I'm intrigued, but I can't finks.

>-Nick


Sorry my limited account doesn't let me send mail off campus so I have to
reply by posting. Actually the warning about Superclock is not in the 
manual but in the release notes to Think Pascal 3. It took me a while to 
find it again. The warning in full reads:

"4. Problem INITs

Several INITs wreak havoc with the THINK Pascal debugging environment,
usually because they bottleneck the Get
in a non-standard fashion. INITs to avoid include Superclock, MacroMaker,
Automac III, Masterstrokes, and TOM (Tear Off Menus). Also, if you are
using a Radius TPD of FPD monitor, don't use the INIT software provided.
The monitors work fine without the INITs and the INITs misbehave with
THINK Pascal."

As I said before this applies to Think Pascal, and I am only assuming that
it may also apply to Think C. Also from my limited experience it is 
evident that Superclock does not INVARIABcal.
So it may be possible to operate for some time before hitting a situation
in which an incompatibility becomes evident.

Hope this helps,
Neale Hays