X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Message-ID: <4111BC57.4723B4BC@yahoo.com>
From: CBFalconer <cbfalconer AT yahoo DOT com>
Organization: Ched Research
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: parse error
References: <ACAAE6BD7520AB4CB2744D1D1BAD3A2BA14504 AT jupiter DOT insideai DOT com> <1091652828 DOT 239126 AT proxy2 DOT srv DOT ualberta DOT ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 23
Date: Thu, 05 Aug 2004 05:32:54 GMT
NNTP-Posting-Host: 12.76.134.180
X-Complaints-To: abuse AT worldnet DOT att DOT net
X-Trace: bgtnsc04-news.ops.worldnet.att.net 1091683974 12.76.134.180 (Thu, 05 Aug 2004 05:32:54 GMT)
NNTP-Posting-Date: Thu, 05 Aug 2004 05:32:54 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

John Hanley wrote:
> 
... snip ...
> 
> I found the problem.  It makes sense that it was a parse error
> because it was one "}" short.  However, it was somewhere in the
> middle of my code, not at the end.  The error message really
> threw me off.  But that's ok.  At least I found the problem.

You multi-posted this to various groups.  You should have
cross-posted the original enquiry to the same groups, with
follow-ups set to the one group of primary interest.  I think it
did little harm this time, but using the appropriate technique in
future will avoid both long interminable threads and the nuisance
of seeing the same query many times.

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?