Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic

Re^2: RFC: A simple and badly-named logging module

by radiantmatrix (Parson)
on Feb 22, 2006 at 17:43 UTC ( #532035=note: print w/replies, xml ) Need Help??

in reply to Re: RFC: A simple and badly-named logging module
in thread RFC: A simple and badly-named logging module

I've put most of these on my todo list, excellent suggestions! Some points...

  1. I agree that the TDIWX set is better than the longer versions, though I think I might make that configurable.
  2. Using $0 and @ARGV are good ideas, but if this is used in a module, not a script, that isn't useful. And, since it's very easy for a script author to simply info 'Started '.$0.join(' '.@ARGV);, I have a hard time justifying that as default module behavior. I'd be interested in opposing arguments if I'm missing something.
  3. PID logging is a good idea, but I will be keeping the sequence numbers as an option (appended to the PID).
  4. I see your points about the ISO8601 format. Enough, in fact, to make the strftime format param configurable. However, I'm leaving 8601 as the default because its a standard, and I think standards make the most reasonable default. Hopefully, with the configurable format, everyone wins.

Thanks so much for the feedback! Extremely useful.

A collection of thoughts and links from the minds of geeks
The Code that can be seen is not the true Code
I haven't found a problem yet that can't be solved by a well-placed trebuchet

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://532035]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others rifling through the Monastery: (3)
As of 2021-01-27 05:15 GMT
Find Nodes?
    Voting Booth?