Re: Replacing "use base" with "use parent"

2012-10-10 Thread Steve
se 'parent' and show the light to its users. Olivier. FWIW, these all seem like legitimate reasons to abolish the use of Base.pm within Moose. Our company uses Moose and 5.8.8 perl currently, so even though there may be a few tweaks necessary, it seems like the right thing to do. Steve

Re: OO Design Principles/Patterns

2011-10-11 Thread Steve
when using perl. That said, I do agree that some don't appear to be particularly relevant to our language of choice! Thanks again, Steve On 10/11/2011 10:01 AM, Stevan Little wrote: On Oct 11, 2011, at 9:02 AM, John Napiorkowski wrote: From: Steve To: "moose@perl.org" Sent: Tues

OO Design Principles/Patterns

2011-10-11 Thread Steve
ose. The only thing I've seen referenced is how Moose 'almost' can be used to create an abstract class with roles. This might be good subject matter for a book on Moose! Steve

Moose users in Grand Rapids Michigan?

2010-05-13 Thread Steve
rk for is investigating Moose and Catalyst as development tools and we would like to have a local source of help. If any of the above gets you curious, email me personally . Thx, Steve

Re: Fwd: Fwd: Re: What's the best approach for translating an attribute upon creation?

2010-02-26 Thread Steve
Thanks for that bit. I changed my code so that I am calling a method from my BUILDARGS sub. This seems to be working quite nicely. Steve On 2/26/2010 2:30 PM, Jesse Luehrs wrote: On Fri, Feb 26, 2010 at 12:52:44PM -0500, Steve wrote: I've moved on to a slightly more complex situ

Re: What's the best approach for translating an attribute upon creation?

2010-02-26 Thread Steve
and I'm sure there are more elegant ways to 'getter done', but this works. Now on with life... On 2/26/2010 12:52 PM, Steve wrote: I've moved on to a slightly more complex situation. The same phone call record contains two different date fields. One is a string like &#

Fwd: Fwd: Re: What's the best approach for translating an attribute upon creation?

2010-02-26 Thread Steve
;ve identified that by the time the subroutine gets called, I have no reference to either the date, or my object. elsif ($d =~ \d\d\/\d\d) {$d = &explodeDate;} sub explodeDate { my $self = shift; # Nothing here... } Is this proper use of coercion, or is there a better way? If I'

Fwd: Re: What's the best approach for translating an attribute upon creation?

2010-02-26 Thread Steve
This method works great! I was very close to getting coercion to work, but somehow my substitution returned '2' every time. Thanks all for the help Steve Something along the lines of the following should work: package Types; use Moose::Util::TypeConstraints; # note, need a

What's the best approach for translating an attribute upon creation?

2010-02-26 Thread Steve
and my WirelessNumber attr. isa 'Str' currently. Also, I can't modify the value passed into my constructor, as it is used for many different tables. Any suggestions are greatly appreciated. Steve