Related articles |
---|
berkeley yacc on DOS lhhuang@jeeves.waterloo.edu (1992-07-11) |
Re: berkeley yacc on DOS epang@sfu.ca (1992-07-13) |
berkeley yacc on DOS wolff@alpha.ces.cwru.edu (Francis Wolff) (1992-07-13) |
Re: berkeley yacc on DOS tom@smart.bo.open.de (1992-07-14) |
berkeley yacc on DOS jar@cheops.HQ.Ileaf.COM (1992-07-20) |
Re: berkeley yacc on DOS moss@cs.umass.edu (1992-07-21) |
Newsgroups: | comp.compilers |
From: | moss@cs.umass.edu (Eliot Moss) |
Organization: | Dept of Comp and Info Sci, Univ of Mass (Amherst) |
Date: | Tue, 21 Jul 1992 13:25:58 GMT |
References: | 92-07-024 92-07-063 |
Keywords: | yacc, MSDOS |
Jim pointed out problems porting yacc to DOS because of 16 bit integers,
limits of 64K bytes in malloc, etc. I don't know exactly when we should
declare pre-386 machines dead, but when we can, we can use 32 bit flat
addressing models for porting such programs, as has been done for GNU
emacs, gcc, bison, TeX/LaTeX, dvips, ghostscript, etc. Some of these have
non-386 versions, but some notably do not, and the 386 versions are
generally faster and offer more capacity since they breakthe 640K bytes
barrier. Anyway, if people want a yacc for DOS and they have 386 or 486
machines, I suggest bison.
--
J. Eliot B. Moss, Associate Professor
Department of Computer Science
Lederle Graduate Research Center
University of Massachusetts
Amherst, MA 01003
(413) 545-4206, 545-1249 (fax); Moss@cs.umass.edu
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.