use Perl

• This is unforgivable! (Score:1)

  by nothingmuch (5848) on 2009.06.16 6:12 (#69076) Homepage Journal

  I think the problem is that a significant part of the process of understanding a difficult concept involves finding the right names for the right concepts. Once you know them it's tempting to take them for granted, because this is a powerful tool for describing what you mean.

  I think your three compact rules really hit the nail on the head. While my third post addresses what you can do when the hierarchy gets complicated, it has nothing on how to get strated developing good habits.

  Anyways, thanks for posting on this important topic from another POV, I think that's the type of dialogue that really helps to build a community (not to mention my ego).

  Hopefully we (the Perl community) willl be writing more robust and reusable code as a result =)

  Reply to This

  • Re: (Score:1)

    by zby (4817)

    OK - so I have a Moose question here. Let's say I have a function to compute an attribute - and I want to call it at the creation time - how can I do that (coercions would not work here - because the type of the parameters is the same as the real value of the attribute and I do want to set that value sometimes).

    To be more concrete, and to tie that with the original subject: in FormHandler we have attributes called 'params' and 'input', input is computed from 'params'. I think we could get rid of 'params
    • Re: (Score:1)

      by nothingmuch (5848)

      You can make 'params' be a private attribute with a public init arg, and input a lazy readonly attributed whose builder method uses the private params.
      • Re: (Score:1)

        by zby (4817)

        Thanks - I'll keep that in mind. It does not buy too much though - still two pieces of state to keep (even though one private).