I don't see why this wouldn't work from a technical perspective. Inside-out objects are just objects, after all. Do you have a particular concern about it? Or sample code?
I think the bigger question is whether a tied array is really the right interface. If you want pop and shift semantics, why not use methods?
$obj->shift() $obj->pop()
From the sound of it, though, you don't really want full array semantics, you just want the sugar of writing 'shift @tied'. On a pop, do you really want to exhaust and cache the iterator to find the last value to return? Do you want it to be expanded in a for loop:
for my $match ( @tied_result ) { # ... }
It seems like tying an array creates more interface confusion and likelihood for misuse.
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
In reply to Re: Combining "tie" and Inside-Out Objects
by xdg
in thread Combining "tie" and Inside-Out Objects
by rjray
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |