Article View: comp.lang.postscript
Article #7459Re: An Idea to Help Make Postscript Easier to Read (and Write)
From: Brad Clements
Date: Mon, 05 Sep 1988 19:00
Date: Mon, 05 Sep 1988 19:00
23 lines
1391 bytes
1391 bytes
From article <940@helios.ee.lbl.gov>, by forrest@ux1.lbl.gov (Jon Forrest): > I'm a newcomer to Postscript and have been spending lots of time > > Anyway, an idea occurred to me that would help people like me > read (and eventually write) Postscript. I thought I'd run it by > this newsgroup to see what you all think. > > What about a "compiler" that converts standard postscript into > what I'll call infix/function form? In otherwords, the output would Personally, I don't own an HP calculator. I do most of my work in C. But I have done an extensive amount of PostScript coding. I like the odd-ballness of PostScript's 'reverse-polish' notation and I use the stack quite extensively, especially in ways that neither C nor Fortran could ever do, or be made to appear to do. I like it the way it is, and I think that I would get very confused by such an idea. Of course, this is just my personal opinion. I'm sure there are very good reasons for carying through on this idea. Brad Clements
Technical Details
Message-ID:
<1322@sun.soe>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!husc6!mailrus!cornell!batcomputer!sun.soe!bkcReferences:
<940@helios.ee.lbl.gov>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!husc6!mailrus!cornell!batcomputer!sun.soe!bkc From: bkc@sun.soe (Brad Clements) Newsgroups: comp.lang.postscript Subject: Re: An Idea to Help Make Postscript Easier to Read (and Write) Message-ID: <1322@sun.soe> Date: 5 Sep 88 19:00:38 GMT References: <940@helios.ee.lbl.gov> Organization: Clarkson University, Potsdam, NY Lines: 23