Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47068 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38221 invoked from network); 1 Mar 2010 10:02:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Mar 2010 10:02:14 -0000 Authentication-Results: pb1.pair.com smtp.mail=sv_forums@fmethod.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=sv_forums@fmethod.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fmethod.com from 69.16.228.148 cause and error) X-PHP-List-Original-Sender: sv_forums@fmethod.com X-Host-Fingerprint: 69.16.228.148 unknown Linux 2.4/2.6 Received: from [69.16.228.148] ([69.16.228.148:49184] helo=host.fmethod.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 83/D2-16552-5A09B8B4 for ; Mon, 01 Mar 2010 05:02:14 -0500 Received: from [83.228.56.37] (port=2163 helo=pc) by host.fmethod.com with esmtpa (Exim 4.69) (envelope-from ) id 1Nm2S1-0007oh-Qt; Mon, 01 Mar 2010 04:02:10 -0600 Message-ID: To: "Tjerk Meesters" , "Jordi Boggiano" Cc: "Herman Radtke" , References: <4B8A97AF.3060608@seld.be> <4bcbf4711002281200u409f041dm330a328eb546e039@mail.gmail.com> <1199A1E8-7663-4A1F-ACEB-1D2B77569BAE@gmail.com> Date: Mon, 1 Mar 2010 12:02:01 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.fmethod.com X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - fmethod.com Subject: Re: [PHP-DEV] Unserialize is broken From: sv_forums@fmethod.com ("Stan Vassilev") > Hi, > > If visibility is an issue why not just use json_enode/decode for this > case then?it doesn't seem like a typical enough problem to be solved > low-level and json seems fast enough for the job ;-) > Hi, I don't know whether it should be fixed or not, but it definitely shouldn't have received resolution "Bogus" in the bugbase. "Bogus" means the issue doesn't exist as described, is not caused by PHP, or it's part of the expected, intended, documented behavior of the language. In this case the issue is an undocumented edge case, it's counterintuitive, and it's reproducible with the provided code. If it not feasible to fix due to performance reason, the resolution should be "Won't Fix". Marking a real issue as a bogus one deprives people who work on PHP from having a handy log of issues that could be reviewed and possibly fixed at a later point as the egine changes and a solution no longer is a BC or performance issue. It's also insulting to the submitter, who took from his time to file an actual problem and was basically dismissed as uninformed on the issue. Regards, Stan Vassilev