Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53534 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59946 invoked from network); 23 Jun 2011 15:12:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jun 2011 15:12:12 -0000 Authentication-Results: pb1.pair.com smtp.mail=dragoonis@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dragoonis@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: dragoonis@gmail.com X-Host-Fingerprint: 209.85.210.170 mail-iy0-f170.google.com Received: from [209.85.210.170] ([209.85.210.170:61398] helo=mail-iy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 01/21-53684-BC7530E4 for ; Thu, 23 Jun 2011 11:12:11 -0400 Received: by iym1 with SMTP id 1so1907307iym.29 for ; Thu, 23 Jun 2011 08:12:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=V2SbaQsZhXTy2IIGZXuLjD4p+5FA1QKpLd1fwIiv4Z4=; b=hkDY/+G/UPsKTQBLys9/fTD4e//rEsEYVTZSTk5EvoE+k0m/D87fAqan702KdshKrB u1+XjQ1qgn1p9brjhKW1Q9nqdbNAn0pYA+UpU7s1dpX8/XJLUY8eifc4dVOM3JwB6M57 tkUKMS7Rf/BOGqcaruiXrTVFWZtCV/OLVcGnU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Um5s+maxa2Tzmz1uZgo6msE2wFcgVzc4z67sq72mMc4vWqmrZ4GdtyztdLYJVlFCni tRlQwKTkoyGLukmuxxIyXzMs47pdVjRh5rMXYa57gH3rdnPvqpp5GoBuZxC0wWxIZbb0 Oh0V8fkMEvWKv5669D1fQb55n5GtVjqev1HqE= MIME-Version: 1.0 Received: by 10.42.219.68 with SMTP id ht4mr2032080icb.142.1308841928098; Thu, 23 Jun 2011 08:12:08 -0700 (PDT) Received: by 10.42.108.70 with HTTP; Thu, 23 Jun 2011 08:12:08 -0700 (PDT) In-Reply-To: References: <4E0355AE.4080305@php.net> Date: Thu, 23 Jun 2011 16:12:08 +0100 Message-ID: To: Ferenc Kovacs Cc: Stefan Neufeind , internals@lists.php.net Content-Type: multipart/alternative; boundary=20cf30549dc331061104a6628288 Subject: Re: [PHP-DEV] Variable scopes for language constructs (foreach, ...) From: dragoonis@gmail.com (Paul Dragoonis) --20cf30549dc331061104a6628288 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Jun 23, 2011 at 4:09 PM, Ferenc Kovacs wrote: > On Thu, Jun 23, 2011 at 5:03 PM, Stefan Neufeind wrote: > > > Hi, > > > > I've lately discussed with a colleague which scopes of variables exist > > for PHP or would probably make sense. In general I think the general > > idea of having variables available all throughout a function is okay as > > this allows things like > > > > foreach($vals as $v) { > > // ... > > $found = true; > > } > > if($found) { > > // ... > > } > > > > (setting $found inside the loop while still being able to access it > > outside) > > > > But the interesting part is that $v is also still available outside the > > loop (last value). While most people would say this is not a big > > problem, it can become problematic when using references. > > > > foreach($vals as &$temp) { > > // ... > > } > > // ... > > $temp = 5; > > (when you don't think about the reference anymore but want some > > temp-variable) > > > > > > If this has been "throughly discussed" before, please excuse. But if not > > maybe somebody could share his oppinion on the following proposal. > > > > What if we (for example with PHP 5.4 or if not possible maybe with the > > next one) change the behaviour so that > > > > * variables used for key/value in foreach (probably other places?) would > > be limited to that loop-scope > > > > and maybe > > * variable $found in the first example would need to be initialised > > before the loop. Otherwise it would be a new variable inside the scope > > of foreach that would be gone afterwards > > > > and/or maybe > > * allowing to explicitly limit variable-scopes inside blocks, for > > example by allowing var $found somewhere inside a function to allow > > things like > > > > if($a) { > > var $temp; > > > > $temp = 5; > > } > > // and $temp would be gone here; was limited to the scope in which it > > was defined by var > > > > > > Hope this is not too much of a non-sense idea to you :-) > > > > > Hi, > > it was discussed many times on the list, and this behavior is also > documented, see > http://php.net/manual/en/control-structures.foreach.php > > "Reference of a $value and the last array element remain even after the > foreach loop. It is recommended to destroy it by unset()." > > personally I find that weird, and unintuitive, but changin that in a major > or minor version could be changed if we chose to. > > I would like to see, in a future version, the local var of the foreach()'s refcount being dropped to 0 or something similar. Unless it is a by-reference variable in which case it should remain untouched. > Tyrael > --20cf30549dc331061104a6628288--