On February 2, 2010 at 15:45, "Lyndon Nerenberg (VE6BBM/VE7TFX)" wrote:
Having an MH-private namespace for scratch files is certainly the way
to go here. These aren't 'temp files' in the traditional sense, and
none of the usual APIs suit the task at hand.
Actually, we have complete control of where temporary files go.
mkstemp() does not impose any location of where temp files go.
Now tmpfile() probably utilizes the system temporary directory
since there is no ability to provide a template for it.
tempnam() will use the system temp dir if its first argument
Wrt nmh, there are some operations where the temporary file
must go in the operating location. For example, when
the temporary file gets renamed.
I can modify the new functions I implemented to use m_maildir("")
as the default location instead of "/tmp" when no template
Nmh-workers mailing list