Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71948 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82821 invoked from network); 1 Feb 2014 21:40:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Feb 2014 21:40:21 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.99 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.99 smtp99.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.99] ([108.166.43.99:48434] helo=smtp99.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 71/49-30967-4C96DE25 for ; Sat, 01 Feb 2014 16:40:20 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 74AF51B0137; Sat, 1 Feb 2014 16:40:17 -0500 (EST) X-Virus-Scanned: OK Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 9E4AD1B0149; Sat, 1 Feb 2014 16:40:16 -0500 (EST) Message-ID: <52ED69BF.90800@sugarcrm.com> Date: Sat, 01 Feb 2014 13:40:15 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Pierre Joye CC: Derick Rethans , Anatol Belski , PHP Developers Mailing List , Matt Ficken , "Stephen A. Zarkos" References: <52EAF181.3000907@sugarcrm.com> <52ED5FDD.8030101@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [VOTE] 64 bit platform improvements for string length and integer From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > That's where the compiler warnings/errors come to the game. Except for > the situations where one does explicit bad casting, which should be > avoided in the 1st place, if possible. Could you explain how compiler can handle zpp("s", &char_ptr, &len) with len being wrong type? If you show me the way for the compiler to warn on this, you've gone a long way towards convincing me - but so far I've seen no way to do it. And this is for me one of the major points where it could break so many things. Any suggestions? > That being said, I have been advocated warning free php-src for years > now. I think if we ever start php6 then we should really change our The problem is nobody wants to work on it. Nobody even cares too much for keeping unit tests green, which should be way above no warnings in the priorities ladder. We definitely should do it, but how many people would sign up for "no warnings" effort as opposed to "new syntax, yay!" effort? That's like washing dishes instead of playing Minecraft. Don't get me wrong - I'm all for it and will try to dedicate some of my copious free time to it (thanks for the reminder, btw). But can we really pull it off? I hope I'm being too pessimistic here. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227