Of course we won't drop it, but it would contain raw binary data (as
opposed to the rest of the PHP environment in unicode semantics mode).
IMO, it is inconsistent and confusing to the end user.
-A
On Jan 29, 2007, at 3:20 PM, Pierre wrote:
Please, who said we will *drop* the GPC array? That
On 1/30/07, Andrei Zmievski <[EMAIL PROTECTED]> wrote:
Of course we won't drop it, but it would contain raw binary data (as
opposed to the rest of the PHP environment in unicode semantics mode).
IMO, it is inconsistent and confusing to the end user.
I do not follow you. Why would it contain raw
PALANCI Ä°letiÅim ve BiliÅim HizmetleriSONY - TOSHIBA - HP - COMPAQ - CASPER -
DELL - FUJITSU - IBM - ASUS - BEKO - SOLO DIAMOND - ACER VS.
GROUPE F.O.P.
Ä°LETÄ°ÅÄ°M ve BÄ°LÄ°ÅÄ°M HÄ°ZMETLERÄ°
NOTEBOOK ONARIMINDA SÃPER FÄ°YAT
GARANTÄ° SÃ
I know that you developers are willing to help a lot with it, but that you
cannot manage to save the spare time needed to do it the right way. That's
why I would like to propose a simple/small/timeless change in your CVS
commit messages: If you feel that the change need to be documented, place
Your proposal was to have a couple of separate functions that people
would use to access GPC data and retrieve it in Unicode form, no?
-Andrei
On Jan 30, 2007, at 8:39 AM, Pierre wrote:
On 1/30/07, Andrei Zmievski <[EMAIL PROTECTED]> wrote:
Of course we won't drop it, but it would contain ra
