Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!mit-eddie!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!unisoft!gethen!farren
From: farren@gethen.UUCP (Michael J. Farren)
Newsgroups: comp.sys.ibm.pc,comp.unix.questions,comp.unix.wizards
Subject: Re: Porting output of Yacc and Lax to the IBbuM
Message-ID: <212@gethen.UUCP>
Date: Thu, 8-Oct-87 20:13:43 EDT
Article-I.D.: gethen.212
Posted: Thu Oct  8 20:13:43 1987
Date-Received: Mon, 12-Oct-87 04:04:27 EDT
References: <468@aoa.UUCP> <340@ucdavis.ucdavis.edu>
Reply-To: farren@gethen.UUCP (Michael J. Farren)
Organization: Sci-Fido - Unix in Oakland
Lines: 24
Keywords: yacc lax ibm pc
Xref: mnetor comp.sys.ibm.pc:8899 comp.unix.questions:4481 comp.unix.wizards:4808

In article <340@ucdavis.ucdavis.edu> windley@iris.ucdavis.edu (Phil Windley) writes:
>   Since we were not careful with pointers/integers (and
>   on a 32 bit machine, you don't really have to be) the rest runs
>   fine on 68000's, VAX's, etc and crashes a 16 bit machine like the
>   80286.  

Which just illustrates a point:  you DO have to be careful with pointers
and integers, dammit!  You may not KNOW that your code will only ever run
on 32-bit machines.  Give everybody a break, especially those who will
come after you and try and maintain and port your code, and DON'T TREAT
POINTERS AND INTEGERS AS EQUIVALENT! (Emphatic enough?)

As far as the original statement goes, I've had much success creating
parsers with lex and moving the generated lex.yy.c code over to the
PC, and recompiling with MSC.  The functions of the lex library routines
are described pretty adequately in the man page for lex, and aren't
particularly hard to implement independently.


-- 
----------------
Michael J. Farren      "... if the church put in half the time on covetousness
unisoft!gethen!farren   that it does on lust, this would be a better world ..."
gethen!farren@lll-winken.arpa             Garrison Keillor, "Lake Wobegon Days"