Date: Sun, 17 Aug 1997 19:28:03 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Paul Derbyshire <ao950 AT FreeNet DOT Carleton DOT CA>
cc: djgpp AT delorie DOT com
Subject: Re: Parse Error Before '*'
In-Reply-To: <5t186l$pta@freenet-news.carleton.ca>
Message-ID: <Pine.SUN.3.91.970817192719.14271P-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On 15 Aug 1997, Paul Derbyshire wrote:

> That addresses the question of what to do with near and far. It does not
> address the question of what was causing those parse error messages. So,
> the parse error before '*' should be added to the FAQ, with one possible
> cause being listed as far and near, with a note that as a protected mode
> 32 bit compiler GCC needs no far nor near, and to check question 17.7.

Thank you for this suggestion.

Since this is really a C-related question, I'd like to see it asked
here a few more times before I consider it a FAQ.  (Normally, people
know that `far', `near' and the like might get them into trouble and
ask this question in a way that the FAQ refers to it.)