On Thu, Sep 30, 2010 at 08:51:04PM -0400, Ricardo Signes wrote:
> * Hans Dieter Pearcey [2010-09-30T14:35:13]
> > We don't like the fact that lazy_build autogenerates public clear_$attr and
> > has_$attr methods for you. OK, I can get behind that; those often don't
> > belong as part of the "publ
* Hans Dieter Pearcey [2010-09-30T14:35:13]
> We don't like the fact that lazy_build autogenerates public clear_$attr and
> has_$attr methods for you. OK, I can get behind that; those often don't
> belong as part of the "public" API, and yes, people will consider them public
> if they don't have
What you're talking about here sounds a lot like the class implementation method
of "inside-out objects". -- Darren Duncan
Ernesto wrote:
*No Memory Leaks by Design*
The mechanism of creating, storing and loading of objects is explained
on
http://dienstleistung-kultur.de/frost/Frost.html#The_u
On 01/10/2010, at 7:17 AM, Chris Prather wrote:
> I am probably an odd man out in that I often want a public clearer and
> predicate method, or at least I don't mind that one is created for me.
> I happily however will embrace option three if the
> "Moose::Deprecated::LazyBuildPublicMethods" is a T
On Thu, Sep 30, 2010 at 05:13:28PM -0500, Evan Carroll wrote:
> I have two questions:
>
> * Should the Array trait using List::Util permit regexes? i.e.
>
> perl -MList::Util -wE'use List::Util qw/first/; say first {/foo/}
> qw/bar foo bazko bazfoo/'
>
> package Class;
> use Moose;
>
I have two questions:
* Should the Array trait using List::Util permit regexes? i.e.
perl -MList::Util -wE'use List::Util qw/first/; say first {/foo/}
qw/bar foo bazko bazfoo/'
package Class;
use Moose;
has "foo" => ( isa => "ArrayRef", is => "rw", traits => ['Array'],
handles =>
> 1) reuse 'builder', i.e. 'builder => 1' is special cased to be the same as
> 'builder => "_build_$attr"'
>
> Someone said "what about subs named '1'?" but I think we're probably all OK
> with ignoring anyone crazy enough to do that.
I made this suggestion, *years* ago (even providing a patch for
On Sep 30, 2010, at 2:35 PM, Hans Dieter Pearcey wrote:
> We don't like the fact that lazy_build autogenerates public clear_$attr and
> has_$attr methods for you. OK, I can get behind that; those often don't
> belong
> as part of the "public" API, and yes, people will consider them public if th
On 30.9.2010 22:34, Sir Robert Burbridge wrote:
On 09/30/2010 02:35 PM, Hans Dieter Pearcey wrote:
Anyway, we were kicking around ideas for how to get rid of these
clearers and
predicates in #moose-dev. I suggested 3 things:
1) reuse 'builder', i.e. 'builder => 1' is special cased to be the
On 09/30/2010 02:35 PM, Hans Dieter Pearcey wrote:
We don't like the fact that lazy_build autogenerates public clear_$attr and
has_$attr methods for you. OK, I can get behind that; those often don't belong
as part of the "public" API, and yes, people will consider them public if they
don't have
On Thu, Sep 30, 2010 at 02:35:13PM -0400, Hans Dieter Pearcey wrote:
> We don't like the fact that lazy_build autogenerates public clear_$attr and
> has_$attr methods for you
> 1) reuse 'builder', i.e. 'builder => 1' is special cased to be the same as
> 'builder => "_build_$attr"'
>
> Someone
Stevan,
first thank you for clearing up some misunderstanding about KiokuDB.
Frost lacks documentation too, but the basic features are already
explained on the main doc page.
So let me sum up the dragons:
*No Memory Leaks by Design*
The mechanism of creating, storing and loading of objects is
We don't like the fact that lazy_build autogenerates public clear_$attr and
has_$attr methods for you. OK, I can get behind that; those often don't belong
as part of the "public" API, and yes, people will consider them public if they
don't have a leading underscore, even if they aren't documented.
13 matches
Mail list logo