http://www.perlmonks.org?node_id=486718


in reply to Things I Don't Use in Perl

I don't get too excited about any new feature in Perl until it's survived a couple of major versions. A lot of things only sound like good ideas but disappear in the next version. Pseudo-hashes, for instance, died (thankfully), although I still have to deal with their insidiousness with the right versions of Perl.

Some other things I don't use and haven't seen mentioned:

--
brian d foy <brian@stonehenge.com>
Subscribe to The Perl Review

Replies are listed 'Best First'.
Categorized Damian Modules
by TheDamian (Vicar) on Aug 25, 2005 at 23:10 UTC
      I know this is asking a lot, but would it be possible for you to, as you have time, modify the REAMDEs and main POD for those to indicate their production-worthiness? I have seen Switch and Class::Contract used in production and I personally have used Quantum::Superpositions in production-affecting code (to good effect).

      My criteria for good software:
      1. Does it work?
      2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

      This hadn't occurred to me until I read your post, but now I think it would be very useful if submitters to CPAN gave a similar explicit rating to their submissions. For one thing, this would help distinguish those submissions that are made in the spirit of "release early, release often" from those that are, at least in the author's estimation, ready for production. I realize that the author's opinion of his/her module may be inflated (or in some cases deflated) but I think it would be a valuable piece of information nonetheless.

      the lowliest monk

      Don't is kinda interesting..

      I'm a big fan of syntax highlighting.

      If I have a chunka code that I want to ignore, I delete it (it's in some versioning system..), comment it out, pod it..

      This could be cool to sort of... encase it. Ignore it. And still be able to look at code and know it does nothing. And still see the syntax highlighting.
      Hm- I guess I could also just.. not call the code.. Hm.

      I just took a look at Coy. The fact that the documentation is in haiku makes me an even bigger fan of your work than I was already. Sorry to blather, but that's just great.
      I think Don't belongs in the blue debugging/coding aids category. It's a nicer spelling of if( 0 ) for multi-line commenting.

      --
      In Bob We Trust, All Others Bring Data.