Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!unisoft!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think C Request
Message-ID: <8800@hoptoad.uucp>
Date: 24 Oct 89 06:44:18 GMT
References: <541@sunfs3.camex.uucp> <2937@husc6.harvard.edu>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 24

In article <541@sunfs3.camex.uucp> kent@lloyd.UUCP (Kent Borg) writes:
>When the resource file for a project is not available (because I have
>it open ResEdit), Think C should complain instead simply letting my
>program die.

In article <2937@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes:
>	A more flexible way to do it would be to have a check box in
>the "Set Project Type" dialog indicating that a resource file should be
>used, as THINK Pascal does it.
>	Not everybody uses resource files, so giving an error when there
>isn't one is not correct behavior.

That wasn't the complaint at all, Rich.  If you have the resource file
open in ResEdit and you launch your project, Think C says "out of
memory" and that's all.  This is not good bug reporting (and it has
nothing to do with the very different non-error case when the resource
file does not exist).  All that's needed is to check ResError() against
the file already open error and show a correct error message instead of
"out of memory" when this happens.  This is one of those two-minute
changes.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

"Gorbachev is returning to the heritage of the great Lenin" - Ronald Reagan