It should be mentioned that you don't necessarily have access to all these namespaces, e.g. because you are working in a team.
And you don't necessarily know which package to use, because your dealing with different companies with different rules for deactivating employees.
Concerning the performance argument of OOP in Perl, IIRC it's true that method calls are 10 times slower than calling directly!
But it's usually better to have working code before you care about performance.
You can still fall back to direct calls if it's recommended after profiling.
IMHO there is even a syntax for this in OO Perl by using a method reference.
$obj_ref->$method_ref()
e.g. in a costly loop, you just need to request the code-reference when initializing, and you don't even need to change the interface of the method you call!
Perl has it all! =)
Cheers Rolf
In reply to Re^6: Benefits of everything is an object? Or new sigils? (performance)
by LanX
in thread Benefits of everything is an object? Or new sigils?
by LanX
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |