When it happens and you need to refactor the code, it's a real pain in the @$$ ...
I think you don't see this situation, because you already incorporated all the ugly workarounds necessary.
> I think you invent a convoluted solution to a convoluted example.
Nope, actually I am spending lot's of time planing in advance to avoid this situation. (And I don't think I'm alone)
Other can just calmly start to code and easily react afterwards. That's one of the big advantages of OOP.
> Get it by tied(@array) and call whatever you need on that.
OK so I can extend the tied package with methods intead of creating a new one... well certainly an improvement. Thx! 8)
But do you really consider writing something like this
tied(@employees)->list_actives()
to be more readable than
\@employees->list_actives()
or even
$employees_ar->list_actives()
???
Cheers Rolf
In reply to Re^2: Benefits of everything is an object? Or new sigils?
by LanX
in thread Benefits of everything is an object? Or new sigils?
by LanX
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |