Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!haven.umd.edu!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.next
Subject: Re: Postscript
Message-ID: <1991Apr22.211904.8832@ni.umd.edu>
Date: 22 Apr 91 21:19:04 GMT
References: <1991Apr22.212326.26982@csusac.csus.edu>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland, College Park
Lines: 31

In article <1991Apr22.212326.26982@csusac.csus.edu> severyn@athena.ecs.csus.edu (Niles Severyn) writes:
>
>I've been working with the file operator in postscript trying to open
>files for writing (for debugging purposes). The interpreter is quite
>happy to do it, however when I go out and try to find the file, it
>doesn't exist.

Sorry, you lose.

I very much would like to be to use this facility as well to run the
"distill" package, as I used to under Release 1.0.  My understanding
is that this capability was removed in the name of security.  

As a result my existing, working, application stopped working and I'm
stuck without an alternative.  I suppose that I could dig up an Apple
LaserWrite and catch the stuff coming back down the serial port, but
that seems such a shame given that I have a wonderful PostScript
engine right on my desk at work and at home.

Such a shame to cripple one of the best PostScript development
platforms available without making some alternatives available (as at
least one other vendor has) such as restricting the files created to
being in certain directories.

Call your NeXT salesperson and complain.  I'm and disturbed that this
capability was removed, and also that there was no notice of dropping
support for that capability.  I was hoping that it would reapper in
some form in the 2.1 release, but this appears to not be the case.
Please correct me if I'm wrong.

louie