in reply to Re^6: Class::InsideOut - yet another riff on inside out objects.
in thread Class::InsideOut - yet another riff on inside out objects.

my %Mode : Field(rw); # generate accessor + mutator
my %Status : Field(ro); # generate only accessor
my %Connection : Field; # generate nothing

[download]

Like this a lot.

my %Mode : Field(rw custom);

[download]

I'd probably avoid this since it's not something that you can guarantee. You could have an accessor/mutator - but with a different name. You could also have a method that wasn't an accessor/mutator with the same name. In either case the "custom" documentation would end up being inaccurate.

Replies are listed 'Best First'.
Re^8: Class::InsideOut - yet another riff on inside out objects.
by Aristotle (Chancellor) on Dec 21, 2002 at 20:27 UTC
    You could have an accessor/mutator - but with a different name. You could also have a method that wasn't an accessor/mutator with the same name.
    Good catch - pity.. it would have been nice.

    Makeshifts last the longest.

[reply]
Re^8: Class::InsideOut - yet another riff on inside out objects.
by Aristotle (Chancellor) on Dec 22, 2002 at 01:31 UTC

    Actually, I was originally going to suggest some syntax that lets one define their own accessor code. Unfortunately it seems not to be possible to pass anything but strings to the attribute routine, so passing a coderef is out.

    But I guess the generator can check whether a method with the mutator's/accessor's projected name already exists and skip generation if so. It would be easy to define some extra syntax for telling the attribute the desired names.

    # separate methods
my %Foo : Field(r:get_field w:set_field);

# combined mut/acc method
my %Foo : Field(rw:quux);

    [download]
    It would be nice there is some more syntax so the autogenerated accessor can do limited parameter validation without one having to write custom ones for simple cases like 'HASH' eq ref $_1. For more complex cases, the could be something like: my %Foo : Field(rw prew:bar postw:baz postr:quux);

    Makeshifts last the longest.

[reply]
[d/l]
[select]

      Hmmm... this sort of stuff falls over the 80/20 sweet spot for me. I would probably add a hook so sub-classes can customise how accessors/mutators are created. That way you could have:

      package Foo;
use base(Class::InsideOut::SetterGetter);
sub new { bless [], shift };
my %Foo : Field(rw);

package Bar;
use base(Class::InsideOut::Lvalue);
sub new { bless [], shift };
my %Bar : Field(rw);

package main;
my $foo = Foo->new;
my $bar = Bar->new;
$foo->set_foo(12);
print $foo->get_foo, "\n";
$bar->bar = 42;
print $bar->bar, "\n";

      [download]
[reply]
[d/l]
        That's cool too - actually, I like it better.

        Makeshifts last the longest.

[reply]

In Section Meditations