Thumbs up from this corner on the idea.
This functionality would have saved me
a lot of repetitious work in past projects,
writing numerous accessors.
However, it looks like your sample data_to_encrypt line has a syntax
error that makes it a little non-obvious (to me, anyway)
exactly how this would work:
filter => [ sub { "@_" }, qw(user uid), '@{$_->{$_}} groups') ]
Looks like there's an extra closing parens at the
end of group'), probably from
cutting-and-pasting inside the qw() closing parenthesis.
So you're going to scan each argument string for a
-> ("check the field values
for dereference syntax"), and then eval
it if you find one?
Seems sufficient; I can't think of any reason it
wouldn't have sufficed for my past purposes.
| [reply]
[d/l]
[select] |
| [reply] |