PHP 5.6 and master, introduce new php.ini settting. Old
iconv./mbstring. php.ini parameters will be removed for master.
If I understand the RFC correctly shouldn't the use of the old/existing
functions trigger an E_DEPRECATED error as of 5.6 to funnel users into the
new settings? I don't see this anywhere in the associated patch. Shouldn't
this be included or have I misunderstood?
PHP 5.6 and master, introduce new php.ini settting. Old
iconv./mbstring. php.ini parameters will be removed for master.If I understand the RFC correctly shouldn't the use of the old/existing
functions trigger anE_DEPRECATEDerror as of 5.6 to funnel users into the
new settings? I don't see this anywhere in the associated patch. Shouldn't
this be included or have I misunderstood?
Context: https://wiki.php.net/rfc/default_encoding
I'm also a bit concerned about this RFC in general. I think the idea behind
it make sense (consolidate encoding settings), but right now it feels a lot
like http://xkcd.com/927/ (turning 6 ini options into 9). Especially given
the issue with the different charset names between mbstring and iconv, I'm
not convinced that this will be more help than harm.
Also, the most important part of the RFC (htmlspecialchars) doesn't seem
reflected in the patch. Is that not yet implemented or did I misunderstand
something?
Nikita
Hi Nikita,
Context: https://wiki.php.net/rfc/default_encoding
I'm also a bit concerned about this RFC in general. I think the idea behind
it make sense (consolidate encoding settings), but right now it feels a lot
like http://xkcd.com/927/ (turning 6 ini options into 9). Especially given
the issue with the different charset names between mbstring and iconv, I'm
not convinced that this will be more help than harm.
Most applications won't mix multibyte char modules. Even if one did, they
still can change encoding by setting INI from user scripts.
If users use default (UTF-8), it does not matter which multibyte char module
they are using.
I think too many INI settings bad also. Unneeded INIs should be cleaned up
in future version. (PHP6?)
Also, the most important part of the RFC (htmlspecialchars) doesn't seem
reflected in the patch. Is that not yet implemented or did I misunderstand
something?
I'll implement required changes for functions. It's incomplete. I just
don't have
enough time :(
Thank you for the comment.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net
PHP 5.6 and master, introduce new php.ini settting. Old
iconv./mbstring. php.ini parameters will be removed for master.If I understand the RFC correctly shouldn't the use of the old/existing
functions trigger anE_DEPRECATEDerror as of 5.6 to funnel users into the
new settings? I don't see this anywhere in the associated patch. Shouldn't
this be included or have I misunderstood?
Sounds good to me.
I'll change RFC a bit, so that PHP emits E_DEPRECATED and remove
unneeded ini settings in the future version. Perhaps, PHP6?
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net