Hi.
As the "full" unicode support went down with php6, wouldn't it be a
logical step to enable the mbstring extension by default(maybe even
turning it into a builtin ext like phar)?
I think that mbstring is a pretty mature and stable extension, and
there isn't much dependencies so I can't think of reason why we
couldn't do it.
Of course the mbstring.func_overload would still disabled by default
(maybe exporting the mb functions to the 'utf8' namespace? :P), so it
would be a backward compatible change.
What do you think?
ps: maybe it is too late for 5.4, but having it in trunk is still
better than nothing.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
On October-11-11 11:46 AM Ferenc Kovacs wrote:
As the "full" unicode support went down with php6, wouldn't it be a
logical step to enable the mbstring extension by default(maybe even
turning it into a builtin ext like phar)?
I think that mbstring is a pretty mature and stable extension, and
there isn't much dependencies so I can't think of reason why we
couldn't do it.
Of course the mbstring.func_overload would still disabled by default
(maybe exporting the mb functions to the 'utf8' namespace? :P), so it
would be a backward compatible change.
What do you think?ps: maybe it is too late for 5.4, but having it in trunk is still
better than nothing.
The mbstring extension was enabled by default once upon a time, if memory
serves, and as I recall the results were extremely painful. While both PHP
and mbstring have matured significantly since then, I'm old school that way.
Fool me once...
Best,
Mike Robinson
What drawbacks could possibly be brought with mbstring being enabled by
default?
On October-11-11 11:46 AM Ferenc Kovacs wrote:
As the "full" unicode support went down with php6, wouldn't it be a
logical step to enable the mbstring extension by default(maybe even
turning it into a builtin ext like phar)?
I think that mbstring is a pretty mature and stable extension, and
there isn't much dependencies so I can't think of reason why we
couldn't do it.
Of course the mbstring.func_overload would still disabled by default
(maybe exporting the mb functions to the 'utf8' namespace? :P), so it
would be a backward compatible change.
What do you think?ps: maybe it is too late for 5.4, but having it in trunk is still
better than nothing.The mbstring extension was enabled by default once upon a time, if memory
serves, and as I recall the results were extremely painful. While both PHP
and mbstring have matured significantly since then, I'm old school that
way.
Fool me once...Best,
Mike Robinson
--
--
Klaus Silveira
(011) 8564-2492
www.klaussilveira.com
Will PHP really never, ever, ever be unicode by default? It'll always
be a weird special case to not be from the shores of the Atlantic?
On Thu, Oct 13, 2011 at 5:41 PM, Klaus Silveira
contato@klaussilveira.com wrote:
What drawbacks could possibly be brought with mbstring being enabled by
default?On October-11-11 11:46 AM Ferenc Kovacs wrote:
As the "full" unicode support went down with php6, wouldn't it be a
logical step to enable the mbstring extension by default(maybe even
turning it into a builtin ext like phar)?
I think that mbstring is a pretty mature and stable extension, and
there isn't much dependencies so I can't think of reason why we
couldn't do it.
Of course the mbstring.func_overload would still disabled by default
(maybe exporting the mb functions to the 'utf8' namespace? :P), so it
would be a backward compatible change.
What do you think?ps: maybe it is too late for 5.4, but having it in trunk is still
better than nothing.The mbstring extension was enabled by default once upon a time, if memory
serves, and as I recall the results were extremely painful. While both PHP
and mbstring have matured significantly since then, I'm old school that
way.
Fool me once...Best,
Mike Robinson
--
--
Klaus Silveira
(011) 8564-2492
www.klaussilveira.com
--
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com
I agree... in fact, most international developers don't know about this.
They expect that PHP supports unicode by default, creating faulty software.
Sad but true.
Will PHP really never, ever, ever be unicode by default? It'll always
be a weird special case to not be from the shores of the Atlantic?On Thu, Oct 13, 2011 at 5:41 PM, Klaus Silveira
contato@klaussilveira.com wrote:What drawbacks could possibly be brought with mbstring being enabled by
default?On October-11-11 11:46 AM Ferenc Kovacs wrote:
As the "full" unicode support went down with php6, wouldn't it be a
logical step to enable the mbstring extension by default(maybe even
turning it into a builtin ext like phar)?
I think that mbstring is a pretty mature and stable extension, and
there isn't much dependencies so I can't think of reason why we
couldn't do it.
Of course the mbstring.func_overload would still disabled by default
(maybe exporting the mb functions to the 'utf8' namespace? :P), so it
would be a backward compatible change.
What do you think?ps: maybe it is too late for 5.4, but having it in trunk is still
better than nothing.The mbstring extension was enabled by default once upon a time, if
memory
serves, and as I recall the results were extremely painful. While both
PHP
and mbstring have matured significantly since then, I'm old school that
way.
Fool me once...Best,
Mike Robinson
--
--
Klaus Silveira
(011) 8564-2492
www.klaussilveira.com--
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com
--
Klaus Silveira
(011) 8564-2492
www.klaussilveira.com