Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!uxc.cso.uiuc.edu!uxc.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!jpd00964
From: jpd00964@uxa.cso.uiuc.edu
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C bug??
Message-ID: <227700039@uxa.cso.uiuc.edu>
Date: 1 Sep 89 01:25:00 GMT
References: <2741@cbnewsc.ATT.COM>
Lines: 21
Nf-ID: #R:cbnewsc.ATT.COM:2741:uxa.cso.uiuc.edu:227700039:000:960
Nf-From: uxa.cso.uiuc.edu!jpd00964    Aug 31 20:25:00 1989


>       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
> Staff Software Developer
> Symantec Corporation, Language Products Group
> Internet: siegel@endor.harvard.edu
> UUCP: ..harvard!endor!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