[TYPO3-50-general] t3lib_div in FLOW3 missing?
robert at typo3.org
Mon Jul 14 09:57:37 CEST 2008
Am 07.07.2008 um 22:17 schrieb Martin Kutschker:
>> Our initial plan was to use native Unicode support with PHP6, but
>> we had to step back from any expectations regarding the release of
>> PHP6, we switched back to what is the best available charset
>> thingy available right now.
> Does it make sense to anticipate the class/method names etc and mimick
> the API with PHP 5.x? The code works but it possibly could be revamped
> to use only mbstring or use a factory pattern (multiple
> with mbstring, iconv and recode) instead of the endless engine-checks.
(sorry for the late answer)
Unfortunately it won't be possible to anticipate the new syntax because
PHP6 won't come only with a new API but also new cast types which if
now with PHP5 would cause parsing errors.
The t3lib_* stuff is really a monster and as far as I know some people
have problems with it too (running FLOW3 that is) if they don't have
So theoretically this really needs a cleanup, on the other hand it would
be such a waste of energy because we'd dump the whole thing as soon as
PHP6 is there (whenever that will be).
More information about the TYPO3-project-5_0-general