Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!pdn!tscs!tct!chip From: chip@tct.com (Chip Salzenberg) Newsgroups: comp.arch Subject: Re: Compilers and efficiency Message-ID: <2805EE1C.704A@tct.com> Date: 12 Apr 91 17:27:55 GMT References: <27fa3350.6bc2@petunia.CalPoly.EDU> <2803849F.483A@tct.com> <10098@mentor.cc.purdue.edu> Organization: Teltronics/TCT, Sarasota, FL Lines: 28 According to hrubin@pop.stat.purdue.edu (Herman Rubin): >In article <2803849F.483A@tct.com>, chip@tct.com (Chip Salzenberg) writes: >> If Herman would write be so kind as to write a spec for such a >> language, we could try to implement it. > >1. I am not quite sure what you mean by a spec. Okay. Let's suppose that holy grail of programming languages, HROL (Herman Rubin Oriented Language), has been designed, implemented, and tested, and it's in a box on your desk. In the box is a tape, a programmer's reference manual, and an architecture-specific reference manual. Here's your job, Herman: Write that programmer's reference manual. If you feel that you can't write it because you're not sure what should be in it, then obviously you don't know what you want, and I for one would be happy if you would stop lamenting its absence. >2. I am willing to provide a list of such instructions ... Not an instruction reference, Herman, a *language* specification. The instruction set is way down the line from there. -- Brand X Industries Custodial, Refurbishing and Containment Service: When You Never, Ever Want To See It Again [tm] Chip Salzenberg ,