Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68831 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21400 invoked from network); 2 Sep 2013 07:51:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Sep 2013 07:51:37 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.83 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.83 smtp83.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.83] ([108.166.43.83:34105] helo=smtp83.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0A/63-32023-88344225 for ; Mon, 02 Sep 2013 03:51:37 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 9A31350147; Mon, 2 Sep 2013 03:51:34 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id D8C7A500E5; Mon, 2 Sep 2013 03:51:33 -0400 (EDT) Message-ID: <52244384.7030407@sugarcrm.com> Date: Mon, 02 Sep 2013 00:51:32 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Rasmus Schultz CC: Matthew Leverton , PHP internals References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: crc32() and ip2long() return values From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Yes, all of these problems can be solved - I am well aware of that. I am > also painfully aware of how much time it can take to solve them reliably. > > I just would like to see a solution rather than a bunch of work-arounds - > not for my own sake, my problem is solved, but for the sake of every poor > fool who's going to fall into these traps. Sorry if I missed it in the thread - so what is your proposal? Is there a patch/RFC/something else for it? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227