Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] save somewhere else than temp?
Date: Wed, 20 Feb 2008 11:54:20 +0100	[thread overview]
Message-ID: <1203504717-sup-2964@port-ext6.ensta.fr> (raw)
In-Reply-To: <1203442604-sup-2120@south>

Excerpts from William Morgan's message of Tue Feb 19 18:38:11 +0100 2008:
> Reformatted excerpts from nicolas.pouillard's message of 2008-02-18:
> > If  you're  using  Tempfile  then closing the file, delete it. And
> > closing the process can force it to close it's files.
> 
> I am using Tempfile, which has a non-deterministic behavior (at least, I
> can't figure out a pattern) upon crashing: sometimes it deletes the
> files, sometimes it leaves them.
> 
> I guess the answer is to manage my own temporary files, deleting them
> only upon successful shutdown.

Long  time  ago  (when I did more ruby stuffs), I wrote this module (attached)
that  makes  part of a package called core_ex. I found it far more useful than
the default module. Feel free to import it.

-- 
Nicolas Pouillard aka Ertai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: temp_path.rb
Type: application/octet-stream
Size: 5318 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080220/41dbda11/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080220/41dbda11/attachment.bin 


      reply	other threads:[~2008-02-20 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 12:04 marko.myllymaki at iki.fi
2008-02-18 14:34 ` William Morgan
2008-02-18 15:57   ` marko.myllymaki at iki.fi
2008-02-18 22:47   ` Nicolas Pouillard
2008-02-19 17:38     ` William Morgan
2008-02-20 10:54       ` Nicolas Pouillard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1203504717-sup-2964@port-ext6.ensta.fr \
    --to=nicolas.pouillard@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox