Re^3: Subroutines with differing behaviour created from AUTOLOAD

Can you explain what

  my %editable = do {
    no strict 'refs';
    %{"${class}::__EDITABLE__"};
  };
[download]

does please? It looks to me like it's using a filehandle to populate a hash of the attributes that should be editable. Can you give an example of how to use this?
Cheers

davis

It's not easy to juggle a pregnant wife and a troubled child, but somehow I managed to fit in eight hours of TV a day.

Comment on Re^3: Subroutines with differing behaviour created from AUTOLOAD Download Code

Replies are listed 'Best First'.
Re^4: Subroutines with differing behaviour created from AUTOLOAD by dragonchild (Archbishop) on Jun 08, 2004 at 16:55 UTC
Filehandle?? Nonono. Read up on do. Basically, it's a way of wrapping a block around an assignment, kinda like what I've done there. The idea is to directly access the symbol table using a soft (or symbolic) reference to find the %__EDITABLE__ hash in the class of the object being used. This way, we don't have to hardcode the classname in. Better yet would be to provide a method (called editable()?) which would return those values. This would play nicer with inheritance. Of course, the best solution is to have something that walks the @ISA tree, but that gets more complicated. ------ We are the carpenters and bricklayers of the Information Age. Then there are Damian modules.... sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon.* - flyingmoose I shouldn't have to say this, but any code, unless otherwise stated, is untested	[reply]

Replies are listed 'Best First'.

Re^4: Subroutines with differing behaviour created from AUTOLOAD
by dragonchild (Archbishop) on Jun 08, 2004 at 16:55 UTC

Better yet would be to provide a method (called editable()?) which would return those values. This would play nicer with inheritance. Of course, the best solution is to have something that walks the @ISA tree, but that gets more complicated.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

[reply]