Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!dartvax!eleazar.dartmouth.edu!earleh
From: earleh@eleazar.dartmouth.edu (Earle R. Horton)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problem with *Apple* glue for SetClikLoop
Message-ID: <13286@dartvax.Dartmouth.EDU>
Date: 30 Apr 89 03:36:43 GMT
References: <13147@dartvax.Dartmouth.EDU> <13148@dartvax.Dartmouth.EDU> <1681@husc6.harvard.edu> <13197@dartvax.Dartmouth.EDU> <13285@dartvax.Dartmouth.EDU>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: earleh@eleazar.dartmouth.edu (Earle R. Horton)
Organization: Thayer School of Engineering
Lines: 25

In article <13197@dartvax.Dartmouth.EDU>matthews@eleazar.dartmouth.edu
	(Jim Matthews) writes:
>In article <1681@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes:
>>      [Problems installing a custom TE Click Loop]
>>
>>      The "LSP Glue" is supplied to us by Apple, so we're pretty much
>>at their mercy. The bug is that, as you point out, the "SetClikLoop"
>>glue simply smashes the saved click loop.

     After another use of dumpobj, I see that {CLibraries}CInterface.o
as supplied with MPW C v 2.0.2 also uses the same questionable scheme
to implement SetWordBreak and SetClikLoop.  Since the Pascal glue for
MPW 3.0 does this, I would assume that the 3.0 C glue still does, too.

     My personal recommendation is not to use any SetWordBreak or
SetClikLoop glue from Apple at this time.

     Aztec C 3.6c does not supply glue for these routines, but rather
uses macros which install pointers to your routines directly in the
TERec.  They also supply information on writing these custom routines
correctly.  Apparently, not all compiler writers are so much at the
mercy of Apple.
Earle R. Horton

Graduate Student.  Programmer.  God to my cats.