On 05/10/10 15:24, Ernesto wrote:
New Frost version 0.67 is available on CPAN and my homepage.
From the changelog:
0.67 Su. October 3, 2010
- Scalar::Util back in Makefile.PL, corrected doc in Frost
- show version of underlying Berkeley DB in t/100_meta/000_version.t
- t/000_moose_exa
On 07/08/10 14:37, Zbigniew Lukasiak wrote:
On Wed, Jul 28, 2010 at 2:55 PM, Oliver Charles
wrote:
I think having Role:: in the package name is important, and it does convey
information about the function of a module. A role has a use case that is
substantially different from a class
inly not
random at all - so please don't start getting overly subjective here. In
regards to SubExporter doing method installs, yes I would probably also
put that in a separate namespace - I believe this is what the Mixin
namespace is for.
--
Oliver Charles / aCiD2
I should also mention if you want to be able to change the Type
internally, but not expose it as part of the public API, you could use
a private writer method (prefixed with _). See the "reader" and
"writer" properties of attributes.
--
Oliver Charles / aCiD2
ou
can't change it's value at all (other than during construction).
--
Oliver Charles / aCiD2
ning.
But if you do have a default value, I guess this could be a way to
capture that (along with default => )
--
Oliver Charles / aCiD2
e;
The code still errors, because you can't call month_name on undef, but
that's your problem ;)
--
Oliver Charles / aCiD2
On Sat, May 29, 2010 at 3:37 PM, Shawn H Corey wrote:
> Hi,
>
> Is the a standard methodology for persistent objects in Moose using SQL?
Well, if you want to serialize objects as they are, you might want to
consider just using KiokuDB with the DBI backend [1]
--
Oliver Charles /
/blob/2132fe392ab9906d6df9be99a9697cf94e2c07de/lib/MooseX/Role/Parameterized/Extending.pod
hope this helps!
--
Oliver Charles / aCiD2
nce you are extracting the value from, for
that attribute. "meta" gives you back the metaclass for a class, not
for an instance, so meta doesn't know what instance you're working
with.
Notice in the example you quoted above from the docs, set_value is
being passed an instance, and a value to set the attribute to.
--
Oliver Charles / aCiD2
return {
1 => "Test::V1",
2 => "Test::V2"
}
}
sub create {
my ($self, $ver, @args) = @_;
my $class = $self->registered_classes->{$ver}
or return;
return $class->new(@args);
}
use Test;
my $foo = Test->create(1);
my $foo2 = Test->create(2, bar => 'yay');
printf "\$foo isa %s\n", $foo->meta->class->name;
printf "\$foo2 isa %s\n", $foo2->meta->class->name;
---
Untested code, but hopefully you get the general idea.
--
Oliver Charles / aCiD2
oach, but it's not
the nicest solution.
--
Oliver Charles / aCiD2
Brilliant, thank you - this was a great asset when I was getting started :)
Keep up the good work!
On Wed, Jan 7, 2009 at 12:49 AM, Oliver Gorwits
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Folks,
>
> The Moose quick-ref card has been updated with a couple of small
> correction
On Wed, Dec 31, 2008 at 5:34 PM, Sean Allen wrote:
> whats cata-moose?
Sorry, I probably should have been a bit more clear. Basically, it's
porting Catalyst to use Moose (more info at
http://jjnapiorkowski.vox.com/library/post/catamoose.html)
On Wed, Dec 31, 2008 at 2:50 PM, John Napiorkowski wrote:
> I'd also add that as we begin to close off the development of DBIC .08100 and
> begin contemplating .09, that's going to be a Moose inspired rewrite
I had a feeling this was the case (after reading more about
Cata-moose) - so I've been
15 matches
Mail list logo
