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_file() that is called by other methods, you want those other methods instead. So I am thinking that File::Temp::Devel or File::Temp::Trace may be a better name, since it will be of most use to developers. Regards, Rob On 16/06/11 21:23 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 > them, e.g. instead of something like /tmp/Hf6254d85.txt, why not call it > /tmp/Some_Package_Name/text_analysing_function-Hf6254d85.txt. > > Anyhow, I think this might be something worth uploading to CPAN. > > So what should it be called? > > I was thinking of something like File::Temp::Smart, for lack of a better > name. But I am open to better ideas. > > Suggestions? > > Rob
