Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62548 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96053 invoked from network); 27 Aug 2012 01:40:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Aug 2012 01:40:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.220.170 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.220.170 mail-vc0-f170.google.com Received: from [209.85.220.170] ([209.85.220.170:54445] helo=mail-vc0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 30/23-13425-C10DA305 for ; Sun, 26 Aug 2012 21:40:44 -0400 Received: by vcbgb30 with SMTP id gb30so4464646vcb.29 for ; Sun, 26 Aug 2012 18:40:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=NzbZHkMzTsxVkhDW9+02HCbOuvJrdNmT9o4ObGsiSBE=; b=gkDo1AaFBVWQFFb8mt2tDMhMwZ+2HDHhJhbVf1L/f0WTvn4WXozMnMFz5XASIJ6W4s amjRiCcQ3BhjvT0LRaHlR63ODNWSZJx5HUSpfaX859z/wEA1Y6adN+u/TU13Z8mN0Chd PMMsx3i8Zy16Bse/caLJbK1BhN86lSZc+c4aJhO2KvFVYKCSJG+GQH+1NHfO1Jg6yqsb mW6n8XwPusfON4zEwhHI8uEVSSAGVZ95PNtgPwfhLTb8YyWJhxKhNi8Qso//BxzRNh+k DdHY+S3VHiAJVVucosq5X7hXk9iQZDTAYDS+M4rl8NArWCInuDR/o7YMDOwdBuvMkAXp JvKA== Received: by 10.52.38.65 with SMTP id e1mr8686416vdk.110.1346031641591; Sun, 26 Aug 2012 18:40:41 -0700 (PDT) Received: from [192.168.200.148] (c-50-131-44-225.hsd1.ca.comcast.net. [50.131.44.225]) by mx.google.com with ESMTPS id w10sm7975174vef.5.2012.08.26.18.40.39 (version=SSLv3 cipher=OTHER); Sun, 26 Aug 2012 18:40:40 -0700 (PDT) Message-ID: <503AD016.4030701@lerdorf.com> Date: Sun, 26 Aug 2012 18:40:38 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Kris Craig CC: Stas Malyshev , Gustavo Lopes , Andrew Faulds , Yahav Gindi Bar , Laruence , PHP Internals References: <503A68F9.9050405@sugarcrm.com> <503A84F3.4080808@sugarcrm.com> <503ACBDD.3080304@lerdorf.com> In-Reply-To: X-Enigmail-Version: 1.5a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQkwd12ty4MMoFFOhYwaJFc3QNVChqMB843WvDBUx1QQzZJ7lSexrXDmZm6sQu6AI36Oyded Subject: Re: [PHP-DEV] Re: [VOTE]Call for voting: support use list in foreach From: rasmus@lerdorf.com (Rasmus Lerdorf) On 08/26/2012 06:34 PM, Kris Craig wrote: > > > On Sun, Aug 26, 2012 at 6:22 PM, Rasmus Lerdorf > wrote: > > On 08/26/2012 06:18 PM, Kris Craig wrote: > > Short of killing ourselves rewriting it in C++, I'm not sure there > > is an ideal solution to this problem. > > Because you think more people can grok C++ than C? That's not my > experience. C is essentially a subset of C++. Any strong C++ developer > (I think I have only ever met 2 of those) will know C inside out. > > > I agree. But keyword there is "strong" lol. In terms of volume, I've > noticed there are far more C++ and C# developers out there who don't > know a lick of C. Makes sense if you think about it, as both are > designed to make the job easier, which in turn also reduces the learning > curve. When I browse through local college offerings in programming, > it's not uncommon for me to see C++ emphasized with no mention of C. > I've always likened it to learning to drive on an automatic > transmission, whereas learning in C is like learning to drive a stick. > It's harder and most people don't do it anymore, even though it's far > more beneficial in the long-run. > > I guess the premise I was alluding to was that, if PHP was written in > C++, there would be a much larger /quantity/ of developers with a > compatible skillset. You're right in that most of them would almost > certainly be lacking in quality, but it would theoretically increase > participation nonetheless IMNSHO. ;) That doesn't make any sense because they still wouldn't be able to understand the code. If you can't read a PHP written in C you definitely won't be able to read a PHP written in C++. And it would still be a yacc grammar or perhaps antlr and if you don't know the difference between a LALR and an LL grammar which language these tools spit out isn't going to make any difference at all. There are way more complicated concepts involved here than the implementation language. -Rasmus