You couldn't have picked a worse time to mention Perl::Compare really.

The normalization overhaul has taken something that did about 10-15 normalization "things" and now only has one (removal of insignificant things like whitespace/pod/comments).

The original (and still current to some degree) intent of PPI-style normalization is to check to see if changes to code "matter" or not.

For example this:

my $foo = 1; # comment
[download]

Is "equivalent" to this:

my      $foo=1  ;
[download]

As the library of normalization functions grows back towards (and past) what the original and now abandoned Perl::Compare implementation had, it is only really intended to factor out changes like:

'foo'      ---> "foo"
"foo$bar"  ---> "foo${bar}";
etc... etc...
[download]

One idea was to let other people edit "your" code, while being certain that they haven't actually changed anything.

I'm sure you can think of others.

In any case, the three above example may well be different, especially if they are object with overloaded operators.

---

---

• 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.