Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!asuvax!ncar!ico!rcd From: rcd@ico.isc.com (Dick Dunn) Newsgroups: comp.lang.postscript Subject: Re: Compiled PostScript Summary: wanna see it again? Message-ID: <1990Jan14.065405.16860@ico.isc.com> Date: 14 Jan 90 06:54:05 GMT References: <28@macuni.mqcc.mq.oz> <550@jvc.UUCP> Distribution: comp Organization: Interactive Systems Corporation, Boulder, CO Lines: 17 In article <550@jvc.UUCP>, lpw@jvc.UUCP (Lance Welsh) writes: > If these people think that parsing PS and writing grammars is a trivial snap: [...I had written...] > > The BNF of PostScript is so trivial it's (a) uninteresting and (b) > > unhelpful. The parser is a snap;... ... >...then why have we never seen anyone post a BNF for postscript or a > public domain parser? I'll bet it's harder than they think. If you knew, you wouldn't have to bet! I posted the BNF, but I'm not surprised you missed it, since it was only two lines long (and even that was loquacious). -- Dick Dunn rcd@ico.isc.com uucp: {ncar,nbires}!ico!rcd (303)449-2870 ...Mr. Natural says, "Use the right tool for the job."