Xref: utzoo comp.sys.next:11224 comp.lang.postscript:7183
Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!rutgers!att!news.cs.indiana.edu!news.nd.edu!mentor.cc.purdue.edu!purdue!haven!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.next,comp.lang.postscript
Subject: NeXT Release 2 Display PostScript: the file operator
Keywords: file
Message-ID: <1991Jan4.142629.20180@ni.umd.edu>
Date: 4 Jan 91 14:26:29 GMT
Sender: usenet@ni.umd.edu (USENET News System)
Followup-To: comp.sys.next
Organization: University of Maryland, College Park
Lines: 15


Does anyone know how the "file" operator is working under NeXT Release 2.0's
Display PostScript server?  Specifically, when I open a file for writing, where
does the file get created?  If I do:

	/f (/tmp/foo) (w) file def

the operation succeeds.  In fact, I can then do writestring operators using the
file handle without errors.  Problem is, the file doesn't get created as
/tmp/foo!  Opening a file for reading seems to work ok.

I was using this capability to run the distill package, which was very
convienient to use on the NeXT as it just created the distilled file.

louie