Hi Stas On Thu, Aug 8, 2013 at 10:03 AM, Stas Malyshev <smalys...@sugarcrm.com>wrote:
> > Personally, I would not use numeric index. > > However, users are expecting it to work and there is no way to raise > > I don't think it is reasonable to expect it to work, it never worked, it > never was documented to work and there's no real use case for it. I also think this limitation was documented, but it seems it gone (or I missed) > The limitation is come from register_globals and it has nasty problem. > > I don't see how is it a nasty problem if there's actually no good reason > to do this. If there is a good reason to do it, please tell what it is. PHP Notice: Unknown: Skipping numeric key 1 in Unknown on line 0 https://bugs.php.net/bug.php?id=65359 This error occurs at shutdown. Removing unneeded limitation is good reason IMHO. If there is $_SESSION[$key] = $var; It's very hard to find what is and where is wrong. > > Most users don't care what serializer does and users who may have > > BC issue can use old serializers anytime. > > Using old serializer is work which we would make users do for > improvement that practically nobody needs and that does not provide any > actual improvement that can not easily be achieved otherwise. Breaking > BC just because somebody somewhere needs an exotic feature that can > easily be worked around doesn't look like a good idea to me. I should have mentioned that new serializer not only allow numeric index, but also allow special characters due to the implementation. i.e. ! and | may be used with the new serializer. Removing unneeded limitations, rather than forcing them to users, is user friendly and the way to go. IMHO. Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
