
Hi, it appears that ghc (and ghci) create temporary files in /tmp during the un-lit phase, at least. It would be nice, if ghc would ... - create those files with read/write permission for the owner only, 0600. - set-up some atexit(3) job, or whatever, to make sure those files _are_ deleted when ghc exits. It might even be possible to create the file and then remove(3) it, right away. The file handle will continue to work, but there is never an entry in the file system. Just a suggestion. :-) Peter

Peter Simons wrote:
it appears that ghc (and ghci) create temporary files in /tmp during the un-lit phase, at least. It would be nice, if ghc would ...
- create those files with read/write permission for the owner only, 0600.
Note that ghc honours TMPDIR (Unix) or TMP (Windows), so you can have
these files stored in a private directory.
--
Glynn Clements

In local.glasgow-haskell-users, you wrote:
It might even be possible to create the file and then remove(3) it, right away. The file handle will continue to work, but there is never an entry in the file system.
IIRC this is not possible because files are referenced in the different phases by name. If nothing goes wrong, temporary files should be deleted. -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME rage against the finite state machine
participants (3)
-
Glynn Clements
-
Peter Simons
-
Volker Stolz