Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!world!siegel
From: siegel@world.std.com (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK Pascal bug? (was Re: SFGetFile Problems in THINK Pascal 3.0.1)
Message-ID: <1991May16.211542.25890@world.std.com>
Date: 16 May 91 21:15:42 GMT
References: <1991May3.182555.10441@...!asuvax!gtephx> <1991May14.183620.7561@...!asuvax!gtephx> <1991May15.200222.12702@...!asuvax!gtephx>
Organization: Symantec Language Products Group
Lines: 27

In article <1991May15.200222.12702@...!asuvax!gtephx> pfluegerm@...!asuvax!gtephx (Mike Pflueger) writes:
>
>Well, I found it.  My fault I guess - when I switched from 2.03 to 3.01
>and TP 3.01 rebuilt my project, I didn't replace the Interface.lib and
>Runtime.lib files in the project.  I incorrectly assumed that TP really
>WAS converting the project.
>
>When I replaced these two files in my project with the 3.01 versions
>and rebuilt the application, everything worked fine.
>
>Now my question is - if TP is converting the project for a new version,
>why isn't it smart enough to replace libraries in the project with the
>new versions?

	The project document is merely a list of the files referenced by the
project, and not the files themselves. The library files themselves exist
on disk as separate files, not in the project.

R.



-- 
-----------------------------------------------------------------------
Rich Siegel                              Internet: siegel@world.std.com
Software Engineer                        Applelink: SIEGEL
Symantec Languages Group