Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!ogccse!orstcs!prism!gixb
From: gixb@prism.cs.orst.edu (Brian Gerard Gix)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C bug??
Message-ID: <12354@orstcs.CS.ORST.EDU>
Date: 2 Sep 89 03:12:51 GMT
References: <2741@cbnewsc.ATT.COM> <227700039@uxa.cso.uiuc.edu>
Sender: usenet@orstcs.CS.ORST.EDU
Reply-To: gixb@prism.CS.ORST.EDU (Brian Gerard Gix)
Organization: Oregon State Univ. -- Computer Science
Lines: 35

In article <227700039@uxa.cso.uiuc.edu> jpd00964@uxa.cso.uiuc.edu writes:
>
>>       Either way, this behavior is a side effect of THINK C's tree scheme;
>>because both files come from the same tree, THINK C thinks that the file
>>you're trying to open is already open.
>>      For this reason, it's wise not to put your works in progress in the
>>tree rooted at THINK C, a fact which is documented. I think.
>>Rich Siegel
>
>Is side effect the new term for bug?  I still like documented feature.
>
>BTW- Rich, where is this "side effect" (bug to the rest of us) documented?
>It's not in the tutorial about projects, and I cannot find it in the overview.
>I've also skimmed through the entire chapter devoted to setting up projects,
>and they say that you only need a folder.  I cannot find where your lovely
>"side effect" (still bug and becomming undocumented feature for the rest of us).
>
>Michael Rutman

Funny, I found the documentation on this bug/feature... it's at the end of
chapter 9 pg 108... :
"Just as you can't have two files with the same name in the same folder, you
shouldn't have duplicate file names in different folders within the project or
THINK C Tree. If you do, THINK C won't know which file to use."

gotcha Michael :-)

--Brian


////////////////////////////////|\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
////// Brian Gix		| gixb@prism.cs.orst.edu              \\\\\\
////// 717 SW 4th #6		|\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
////// Corvallis, OR 97333	| to C or not to C.. -apologies to WS \\\\\\
////////////////////////////////|\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\