in reply to RFC - module idea - Devel::StrictObjectHash

Since there are no replies yet, I thought I'd at least give you some feedback. I think the idea here is neat. The interface looks nice, and the idea seems well thought out. That said, I probably won't use this module, for the same reasons I don't use Tie::SecureHash. Maybe I'm just lazy, and maybe I'm overly confident, but I've never really had a problem with plain, unsafe hash-based objects. If I do, though, hopefully I'll remember your module. It seems like a nice solution.

  • Comment on Re: RFC - module idea - Devel::StrictObjectHash

Replies are listed 'Best First'.
Re: Re: RFC - module idea - Devel::StrictObjectHash
by stvn (Monsignor) on Apr 22, 2004 at 18:02 UTC
    revdiablo

    Thanks for your reply. I hear what you are saying, personally I have never really had a problem either with hash-based OO. But then again, I never wrote automated tests either until recently, and after doing so, I was surprised by how much more confident I was in my code. Then after I started using Devel::Cover along with the tests, it was like being able to see my code in a whole new light. Now not only was I confident my code worked (tests), but I knew how much of my code is worked by the tests (code coverage). I hope Devel::StrictObjectHash will go along with tools like these. And just give you that extra added layer of confidence. It funny, cause the idea really is that running the module wont actually do anything, because that means your code is correct :)

    -stvn
      I never wrote automated tests either until recently

      This is another practice that seems like a great idea, but I'm just too lazy to force myself to do it. Some day, I vow, I will write test suites for my code. It's just so hard to do when the code I write is usually used by 1 user: myself... [I know, excuses excuses]

      the idea really is that running the module wont actually do anything, because that means your code is correct

      Indeed, this makes me think of using strict. It's not there for when things go right, it's there for when things go wrong. And of course, since I'm such a big fan of strict, it makes a hypocrite out of me when I say "I've never had a problem with unsafe hashes." I guess I'll just have to live in this state of limbo until I get my act together. 8^)

        Indeed, this makes me think of using strict.

        Exactly! Thats what I am going for.

        -stvn