Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!dartvax!eleazar.dartmouth.edu!isle
From: isle@eleazar.dartmouth.edu (Ken Hancock)
Newsgroups: comp.sys.mac
Subject: THINK Pascal 2.0 Link errors
Message-ID: <12278@dartvax.Dartmouth.EDU>
Date: 18 Feb 89 02:11:01 GMT
Sender: news@dartvax.Dartmouth.EDU
Reply-To: isle@eleazar.dartmouth.edu (Ken Hancock)
Organization: Personal Computing Center, Dartmouth College
Lines: 34


Has anyone else besides me been having trouble with THINK
Pascal 2.0 Link errors?  I was writing a small application
today to turn off AppleTalk and then launch a program.
I included the AppleTalk.p library with the appropriate
"uses AppleTalk;" line in my program.  Called an MPPClose,
compiled it, and got a "undefined: 'MPPCLOSE'".

Feeling very stupid, I looked through all the build orders,
code, etc.  I saw nothing wrong.  Asked someone else who was
very familiar with Pascal.  "Nope, that's right."  Asked someone
else.  "That's right.  It should work."

Well, it doesn't.  I called Tech support and someone tried
very hard to help.  They tried out a simple program,
it didn't work.  So, they tried it with an additional
interface added and another couple calls.  Then it worked.
Made a spelling error which the debugger informed him of,
removed it, and then removed the extra interface.
All of the sudden, MPPClose compiles fine.  He didn't know
how he did it.

So, that leave me in the dark.  I still can't get mine to work.
He said he'd report the bug and had had a couple other bugs
which had mysteriously appeared and disappeared.  Rich,
do you know of a bug fix that's coming?  Think Pascal 2.0p1?

Ken


Ken Hancock  '90                   | BITNET/UUCP/
Personal Computing Ctr Consultant  |   INTERNET:  isle@eleazar.dartmouth.edu
-----------------------------------+----------------------------------------
DISCLAIMER?  I don't get paid enough to worry about disclaimers.