I am in the design phase of an O.O. project and have had the idea of a sketchy concept called 'filtering'. I have done an internet search and found a couple of publications that detail 'filtering' as an object concept. Basically, filter objects consist of conditions that have to be met by the object bundle being filtered. Each filter 'cassette' (my term) specifies conditions relating to one of the objects of the 'bundle' (bundle:- I think that this is a commonly used OO word) being passed through the filter system. I am thinking of using an XML setup to hold the cassettes and the details relating to these cassettes.
I suspect that Java is the language that would most suite this. This partly because my reading of O.O. programming has centred on Java. And I don't really understand the conceptual differences between object orientation in Java and Perl. What I do understand is that Java uses interfaces whereas Perl does not. And Java regards more things as objects than Perl. And Perl does not have constructor classes (what Perl has instead of this I am not sure). That's about all.
My questions relating to this are: 1. Are there any other terms for 'filtering'? 2. Does anyone have examples of code relating to filtering? 3. Does anyone have examples of XML schema for storing Java or Perl objects? 3. What is the best information source detailing differences between Perl and Java with regard to object orientation?
In reply to Filter objects? by matth
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |