Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!samsung!emory!gatech!udel!ee.udel.edu
From: new@ee.udel.edu (Darren New)
Newsgroups: comp.sys.next
Subject: Re: only PS fixed in 2.1?
Keywords: OS 2.1, PostScript
Message-ID: <47466@nigel.ee.udel.edu>
Date: 13 Mar 91 15:35:07 GMT
References: <27413@uflorida.cis.ufl.EDU> <1991Mar13.064804.16235@agate.berkeley.edu> <1991Mar13.144929.25876@ni.umd.edu>
Sender: usenet@ee.udel.edu
Distribution: na
Organization: University of Delaware
Lines: 21
Nntp-Posting-Host: snow-white.ee.udel.edu

In article <1991Mar13.144929.25876@ni.umd.edu> louie@sayshell.umd.edu (Louis A. Mamakos) writes:
>For example, rather than completely disabling opening files for
>writing, NeXT could have (like DEC did with their Display PostScript)
>restricted the directories that the file could exist in.  While this
>is a minor inconvienience, it certainly is preferable to losing the 
>capability entirely.

I would imagine that most uses of the file operators (for writing) are
not for writing, but rather for creating files.  How about an option
that allows writing only to files which were created by PostScript
earlier in the same PostScript session. (PostScript "session" taken to
mean whatever it takes to make this acceptable.)

In that way, fonts and distills and so on could be written out, but it
would take more work to (say) automatically munge EPS files. In any
case, it would certainly prevent deleting the kernel.
-- 
--- Darren New --- Grad Student --- CIS --- Univ. of Delaware ---
----- Network Protocols, Graphics, Programming Languages, 
      Formal Description Techniques (esp. Estelle), Coffee, Amigas -----
              =+=+=+ Let GROPE be an N-tuple where ... +=+=+=