Description:
------------
Will be nice if the filter extension can provide ( maybe for 5.2.1) a built-in, consistent and **ease of use** OOP interface.

I know this can be implemented in userspace, but its much better to have it into the extension.

Something like http://framework.zend.com/manual/en/zend.filter.html

Don't get me wrong, I really like this idea, however, I think programmers out there will be unlikely to use this extension 'cause the lack of an abstract easy way to use it, too much constants, only procedural interface..etc..


actually, if you don't want to ..may I ask Marcus  to implement something like this on SPL.. ? :-)

"SPL is a collection of interfaces and classes that are meant to solve standard problems."

Input filter validation is clearly an standard problem ;-)



Reproduce code:
---------------
nothing..





Expected result:
----------------
well.. I expect **something** like this.


a) a group of get_*() methods acting like FILTER_SANITIZE_* constants.

b) a group of is_* methods acting like  FILTER_VALIDATE_* ..

this is a really basic description of course.







Actual result:
--------------
no class implemented.