Description: ------------ Package is not compatible with running under E_STRICT - methods are not marked as static, so one gets warning when calling e.g. Validate::uri() from other code (such as Services_Facebook). It would be cool to mark all functions as static and private/public as appropriate, to make it possible to run Validate with E_STRICT.

Added patch Validate.php.diff.

Hi Jaromir, Thanks for the patch; but it's unlikely to apply to Validate - we want to maintain php4 compatability for this particular package. That being said, proposals for Validate2 would be more than welcome - this kind of proposal would mean we just push everything up to PHP5 comptability. That being said; I would encourage you to consider a different API approach to avoid "static cling" where possible: making it easy for others to mock out a validate object by avoiding static methods.

I've encountered a package using the static call (Services_Facebook), that's why I made this patch - so you basically consider this bad practice and do not intend Validate (or Validate2) to be called statically?