I'm not sure I agree with this statement, even with its follow-up. In Perl, everything can be implemented as an object if you are willing to do the work; a great example of this is tied stuff. In java, everything short of base types is an object, and even these base types have optional classes built into the language core.
Offhand, my uneducated opinion is that applying strict filters to objects is more instrinsically accomplished with java, with its strong typing, single inheritance, and enforced method signatures, as opposed to Perl with its vague typing (scalar, list, boolean, void), multi-inheritance (use base class1, class2...classn), and pathetic proto-typing. Don't get me wrong, you can do it all with Perl, but it's not built in nearly as strongly to the language itself. If someone wants to kick the crap out of the above assertions, please be my guest. :)
In reply to Re: Re: Filter objects?
by clairudjinn
in thread Filter objects?
by matth
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |