Hi Darby
The revisions you've made to Zend_Loader have thrown up some other
side-effects - and looking closely into the Zend_Filter_Input module
perhaps that's been a good thing!
When I updated my ZF library to trunk, I started getting lots of
E_WARNINGs refering to missing Zend_Filter_NotEmpty and
Zend_Filter_Between. Strange, I thought, they're only validators, not
filters. Try as I could I couldn't shake these warnings (I leave my
dev box as 'chatty' as possible to even throw notices to see if
everything is OK).
When I looked closer into the Zend_Filter_Input class, I found that
there's a method called '_getFilterOrValidator($interface,
$classBaseName)'. It iterates through all the namespaces to find a
matching class - which probably worked noiselessly before, but now, of
course, Zend_Loader throws all these warnings for non-existent classes.
Is there a reason for this performance hog - Zend_Filter_Input I mean?
Is there any likelihood that a filter and a validator will share the
same namespace? Are there any developers out there that would be
adversely affected by a slight refactoring for this - adding
namespaces for either a Validator or Filter so that the loader can be
slightly more efficient?
I'll pop an issue in on JIRA but wanted to raise it here first to
gauge a reaction and see who's the caretaker of this component at
present?
Cheers
--
Simon Mundy | Director | PEPTOLAB
""" " "" """""" "" "" """"""" " "" """"" " """"" " """""" "" "
202/258 Flinders Lane | Melbourne | Victoria | Australia | 3000
Voice +61 (0) 3 9654 4324 | Mobile 0438 046 061 | Fax +61 (0) 3 9654
4124
http://www.peptolab.com
