Hi, "Temp" is indeed for "temporary" but the function still takes a template as parameters. The proposal seems to be to to have a similar function, one that also uses a template, but with the default permissions, not those of a temporary file create by the existing functions. Cheers, Thu 2009/7/25 Thomas Schilling <nominolo@googlemail.com>:
Sorry, I don't get this. I thought the "temp" in openTempFile stood for "temporary" not "template". And what would the signature of these new functions would look like and what exactly they would do.
2009/7/24 Ian Lynagh <igloo@earth.li>:
Hi all,
This is Add openFileTemplate, openBinaryFileTemplate to System.IO http://hackage.haskell.org/trac/ghc/ticket/3393 (originally part of http://hackage.haskell.org/trac/ghc/ticket/2610)
In System.IO, openTempFile and openBinaryTempFile mask the file permissions of the file they create with 0o600. However, we would like to use it for implementing things like writeFileAtomic, in which case we want the default file permissions to be used.
I propose that we add openFileTemplate and openBinaryFileTemplate functions, which use the default permissions.
Deadline: 8th August (2 weeks).
Thanks Ian
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
-- Push the envelope. Watch it bend. _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries