use Perl

• Re: Line Noise (Score:1)

  by Aristotle (5147)

  It’s not Perl that’s line noise, it’s the regex syntax. Last night I wrote this: s{/(?!\.\.)[^/]+/+\.\.(?=/|\z)}{}g
  • Re: Line Noise (Score:2)

    by Dom2 (2981)

    I love the x modifier. :-)

    s{
        /           # Leading slash.
        (?!\.\.)    # No parent directories of root.
        [^/]+       # Pick out the directory name in root.
        /+\.\.      # Match any number of slashes, then parent directory.
        (?=/|\z)    # Assert that there is a following slash (or end of string).
    }{}gx

    So it cleans up pathnames to remove /foo/../bar/../baz to be ju
    • Re: Line Noise (Score:1)

      by Aristotle (5147)

      Even /x only really helps because of your profuse comments, though.

      You guessed correctly: I needed to normalize HTTP URIs to compare them, and URI [cpan.org]’s canonical method doesn’t finish the job. To be precise, this runs in a 1 while s/// loop, which is necessary to handle paths like foo/bar/baz/quux/../../../bar.
      • Re: Line Noise (Score:2)

        by Dom2 (2981) <{dom} {at} {happygiraffe.net}> on 2006.05.03 3:22 (#47538) Homepage Journal

        It's not just the comments. I also find that breaking the regex into its component groups makes it easier to understand. It's what I do mentally anyway, so it just means that it's done already for me.

        -Dom

        Reply to This

        Parent