deprecating (part of) lazy_build

2010-09-30 Thread Hans Dieter Pearcey
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.

Re: [ANNOUNCE] Frost 0.65 - Feasible Referential Object STorage

2010-09-30 Thread Ernesto
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

Re: deprecating (part of) lazy_build

2010-09-30 Thread Karen Etheridge
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 said what

Re: deprecating (part of) lazy_build

2010-09-30 Thread Sir Robert Burbridge
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 a

Re: deprecating (part of) lazy_build

2010-09-30 Thread Jiří Pavlovský
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

Re: deprecating (part of) lazy_build

2010-09-30 Thread Evan Carroll
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 it iirc).

Ping about Traits and List::Util stuff on Array

2010-09-30 Thread Evan Carroll
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 = {

Re: Ping about Traits and List::Util stuff on Array

2010-09-30 Thread Jesse Luehrs
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; has

Re: deprecating (part of) lazy_build

2010-09-30 Thread Tom Lanyon
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 Trait

Re: [ANNOUNCE] Frost 0.65 - Feasible Referential Object STorage

2010-09-30 Thread Darren Duncan
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