Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

Re^6: Class::InsideOut - yet another riff on inside out objects.

by Aristotle (Chancellor)
on Dec 20, 2002 at 18:38 UTC ( #221488=note: print w/ replies, xml ) Need Help??


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

That's something an attribute could very elegantly handle:

my %Mode : Field(rw); # generate accessor + mutator my %Status : Field(ro); # generate only accessor my %Connection : Field; # generate nothing
I'm also thinking it would be nice if one could also write my %Mode : Field(rw custom);
which would not create an accessor, but would test for the existence of one and complain if it didn't find one. That way the code becomes self documenting. Maybe a do-nothing private attribute would be nice to that end as well.

Makeshifts last the longest.


Comment on Re^6: Class::InsideOut - yet another riff on inside out objects.
Select or Download Code
Re^7: Class::InsideOut - yet another riff on inside out objects.
by adrianh (Chancellor) on Dec 21, 2002 at 15:15 UTC
    my %Mode : Field(rw); # generate accessor + mutator my %Status : Field(ro); # generate only accessor my %Connection : Field; # generate nothing

    Like this a lot.

    my %Mode : Field(rw custom);

    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.

      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.

      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);
      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.

        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";

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://221488]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (10)
As of 2014-11-28 12:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My preferred Perl binaries come from:














    Results (196 votes), past polls