perltidy: Picking up the loose ends

If you look closely at the screenshot here, you’ll see where perltidy was at work.

2014-02-27-lv-r1fz6-perltidy

On the left, the venerable mp32ogg, which I picked because it was the first thing I could find that was written in perl and functional.

On the right, its doppelgänger in mp32ogg.tdy, and as scrubbed clean by perltidy.

I’m familiar with tidyhtml, which — as a nonprogrammer — I consider to be as important as washing my hands before I eat.

perltidy is new to me though, most likely because … well, because I don’t program, let alone program in perl. Which I suppose makes me a bit of a barrack-room lawyer.

Purists will tell you that perltidy is a crutch, that you should code like a girl anyway, and perltidy and its ilk make you a lazy coder.

Or you could take my uneducated endorsement, which is based on the long-standing presumption that computers should be doing our dirty work, and cleaning up our mistakes for us. 😉

4 thoughts on “perltidy: Picking up the loose ends

    1. K.Mandla Post author

      It’s coming. I had to collect all the other pdf+title programs and it took longer than expected. pente and perltidy were quicker and easier to handle. … 😉

  1. Pingback: shellcheck: I should probably keep this around | Inconsolation

  2. Pingback: csstidy: Tidy and neat | Inconsolation

Comments are closed.