Thank you!
A very useful script.
I would like to add something to my own version of this script (as soon as I can find the time to do it, sorry ;) ):
- > Log files should speak clear and simple. Those are tools to work with even if the user ignores what the script is doing. After some time, I might forget what was the script doing. When preparing logs for large number of processed files it is easier to read one or two lines clearly identified with each file.
- > Making a more expressive table of regexes that could load inside a hash with different extensions and another generic key that would apply to all files. That would be easy by just starting from a standard template with fields to fill in. (A kind of ini file where lines starting with # wouldn't count as values. And keys would start without any tab character)
- > Modules could make this script useful for any platform!
Then this script could become a very powerful tool!
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|