Date: Sun, 27 Feb 2000 09:48:29 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: ANNOUNCE: Bison 1.28 ported to DJGPP
In-Reply-To: <200002242322.SAA31756@delorie.com>
Message-ID: <Pine.SUN.3.91.1000227094751.14604E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 24 Feb 2000, Mark E. wrote:

> >  2. Some of the files in the binary distribution are long
> >     (e.g. REFERENCES), but others, like bison.sim and bison.inf, are
> >     truncated.  Why?
> 
> bison.sim needs to work in both environments. REFERENCES is just a text file 
> so it doesn't matter if it's truncated.

Actually, my main concern was bison.inf.

> ! +BISON_HAIRY=%DJDIR%/share/bison.hai
> ! +BISON_SIMPLE=%DJDIR%/share/bison.sim

Yes, you are right, djgpp.env needs to be corrected like this.  But
telling users to edit djgpp.env seems like a lesser trouble than
removing support for BISON_* variables.

> >     All this just to correct the decision made years ago to put the
> >     files into the lib subdirectory (because share didn't yet exist)?
> 
> Well, mistakes do deserv be corrected, yes?

Sure.  The question is the price.