On Thu, Jun 16, 2011 at 09:23:50PM +0100, Robert Rothenberg wrote:
> While debugging a project that generated a lot of temporary files, I came
> upon a nifty idea: rather than name the temporary files the usual random
> strings, why not have the files named by the method/function that created
> the
On Sat, 18 Jun 2011 23:36:44 +0100
Robert Rothenberg wrote:
> The module makes use of File::Temp, but the interface is different,
> and I don't think it makes sense to add specialised high-level
> functionality to a low-level module.
>
I agree that it doesn't make sense there. This should be ke
Thank you for the suggestions.
Like Nadim Khemir, I also think that adding an option so that there is also
a log file that gives a stack trace associated with each temp file is useful.
The prototype uses attributes to flag a subroutine as not used in naming,
e.g. if you have a method create_temp
In case you are interested, a prototype is on GitHub at
https://github.com/robrwo/File-Temp-Trace
On Sun, Jun 19, 2011 at 12:51 AM, Bill Ward wrote:
> Oh, I thought it was just about generating the filename using the
> module/subroutine name. *that* should be in File::Temp, and maybe the other
>
Oh, I thought it was just about generating the filename using the
module/subroutine name. *that* should be in File::Temp, and maybe the other
features you describe should be in a new module?
On Sat, Jun 18, 2011 at 6:44 PM, Robert Rothenberg wrote:
> It has a different interface, necessarily. Fi
It has a different interface, necessarily. File::Temp only manages single
temp files or directories in isolation, whereas my module manages a set of
them with logs about how they were created.
On 18 Jun 2011 23:44, "Bill Ward" wrote:
> It's not really that high level or specialized. It's just a ma
It's not really that high level or specialized. It's just a matter of
updating how the file name is generated. I could easily see it going either
way. If you do go with a separate module, the interface should be the same
(with whatever added options needed to add the new features) as File::Temp,
fo
The module makes use of File::Temp, but the interface is different,
and I don't think it makes sense to add specialised high-level
functionality to a low-level module.
On Sat, Jun 18, 2011 at 4:42 PM, Bob Parker wrote:
>
>
> -Original Message-
> From: Robert Rothenberg
> Reply-To: Rober
-Original Message-
From: Robert Rothenberg
Reply-To: Robert Rothenberg at CPAN
Date: Thu, 16 Jun 2011 21:23:50 +0100
To: Perl Module Authors List
Subject: Need suggestions for a module name
>While debugging a project that generated a lot of temporary files, I came
>upon a nifty idea:
HI,
Using ::Smart may not be so smart
I have no idea for the module name but one or two about the
functionality it coold offer. IMO, a module just for that functionality,
although, welcome, is over the edge. maybe adding some functionality
could make it worth istalling. i also wonder if there isn
'Smart' is subjective, and not very informative. How about
File::Temp::ByFnName ?
-Original Message-
From: Robert Rothenberg [mailto:r...@fastmail.net]
Sent: Thursday, June 16, 2011 9:24 PM
To: Perl Module Authors List
Subject: Need suggestions for a module name
While debugging a proje
11 matches
Mail list logo
