Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53302 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32493 invoked from network); 16 Jun 2011 05:23:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jun 2011 05:23:58 -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 67.192.241.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.163 smtp163.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.163] ([67.192.241.163:32819] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 42/04-24246-C6399FD4 for ; Thu, 16 Jun 2011 01:23:57 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp26.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id D380780134; Thu, 16 Jun 2011 01:23:53 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp26.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 8CF4A80102; Thu, 16 Jun 2011 01:23:53 -0400 (EDT) Message-ID: <4DF99368.2040508@sugarcrm.com> Date: Wed, 15 Jun 2011 22:23:52 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Pascal COURTOIS CC: PHP Developers Mailing List References: <8757232E56758B42B2EE4F9D2CA019C9014CE547@US-EX2.zend.net> <8757232E56758B42B2EE4F9D2CA019C9014D10DC@US-EX2.zend.net> <4DF9913B.4030404@nouvo.com> In-Reply-To: <4DF9913B.4030404@nouvo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Give the Language a Rest motion (fwd) From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > On every PHP project I work on I had to find workarounds because PHP crashes. > Behaviour bugs (feature not working as intended) are annoying but memory leaks and > memory corruptions are just a no no no in production environment. The only way A key to fixing memory corruption is providing good bug reports - with backtraces, valgrind reports, etc. If you have such reports and nothing happens to them - you may want to try to raise the profile of bug reports that are bothering you by mentioning them on the list and calling for volonteers to fix them. Usually if bug is in frequently used module and reproduceable, there would be somebody who can fix it. > What I need is a very stable language on which I can rely and I'm very sad to > to say PHP is getting worse and worse on that point of view versions after versions. I can not contradict your experience, it is what it is, but my experience for years working with PHP was exactly the opposite. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227