Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!okstate!gregg From: gregg@a.cs.okstate.edu (Gregg Wonderly) Newsgroups: comp.os.vms Subject: Re: Print symboints Message-ID: <3621@okstate.UUCP> Date: 2 Jun 88 01:50:58 GMT References: <757@acer.stl.stc.co.uk> Organization: Oklahoma State Univ., Stillwater Lines: 29 From article <757@acer.stl.stc.co.uk>, by scott@stl.stc.co.uk (Mike Scott): > > Concerning writing print symbionts, Gray.OSBUSouth@Xerox.COM wrote: > >> ... > > ... > > Why do DEC assumed that anyone writing in C wants a u*x - like > environment? It causes quite a few problems like this one. > > Regards. Mike Scott (scott@stl.stc.co.uk...uunet!mcvax!ukc!stl!scott) > phone +44-279-29531 xtn 3133. I think the more important question is why did DEC choose to make the interface to the symbiont (message passing between the JBC and the symbiont) through public I/O channels. This is VERY POOR design in my opinion. They already stole enough functionality by using $HIBER to put the PRTSMB symbiont to sleep while waiting for work. Making the entire PRTSMB symbiont processing into an AST driven machine, is hardly icing on the cake. Grrrrr...... ----- Gregg Wonderly Department of Mathematics Oklahoma State University UUCP: {cbosgd, ihnp4, rutgers}!okstate!nemo.math.okstate.edu!gregg Internet: gregg@NEMO.MATH.OKSTATE.EDU