Xref: utzoo comp.unix.internals:2611 comp.windows.news:2577 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!barnett From: barnett@grymoire.crd.ge.com (Bruce Barnett) Newsgroups: comp.unix.internals,comp.windows.news Subject: Re: X11 bashing Message-ID: Date: 24 Apr 91 02:47:11 GMT References: <28063@uflorida.cis.ufl.EDU> > <=V6&^Q_.19037@cheers.Bungi.COM> <130080@uunet.UU.NET> <4_XAYQ1@xds13.ferranti.com> Sender: news@crdgw1.crd.ge.com Reply-To: barnett@crdgw1.ge.com Followup-To: comp.unix.internals Organization: GE Corp. R & D, Schenectady, NY Lines: 23 In-reply-to: peter@ficc.ferranti.com's message of 23 Apr 91 21:35:53 GMT In article <4_XAYQ1@xds13.ferranti.com> peter@ficc.ferranti.com (Peter da Silva) writes: > >And perhaps > > the language is too awkward; postfix if's are hard to read. > How much actual programming in Postscript would you expect the typical > application programmer to do? I think that depends on the toolkit and development environment. Using tNt 2.0 and DevGuide, you can develop an application interactively, and then link in the toolkit without writing any PostScript at all, I believe. If you want to modify one of the widgets, you have to get into PostScript programming, but it's Object Oriented, so that helps. I agree about the language. The problem is parsing code like foo bar blatz mumble tilderoll You have to know each operator and how many items it pops/pushes off the stack. I really wish there was some way to add parentheses, even if there were syntatic sugar. Too bad all of the bracket characters are defined. I wanted to define a set of brackets to use just to help me balance the operators... -- Bruce G. Barnett barnett@crdgw1.ge.com uunet!crdgw1!barnett