[PATCH] Allow use($var..) statement ubiquitously

On Thursday 17 July 2008 6:23:31 pm Moriyoshi Koizumi wrote:

Hi,

Attached are the patches that allow the "use" statement that was
introduced with closures to appear within every function statement
except method definitions. I think this feature is a good addition
because it resolves inconsistency between closures and unticked
functions. In a nutshell,

<?php
function foo() use (&$some_globals) {
echo $some_globals;
}
?>

is equivalent to

<?php
function foo() {
global $some_globals;
echo $some_globals;
}
?>

While,

<?php
function bar() {
$some_local_var = '';
function fubar() use (&$some_local_var) {
echo $some_local_var;
}
}
?>

and

<?php
function bar() {
function fubar() {
global $some_local_var;
echo $some_local_var;
}
}
?>

are of course not the same.

Which is why I am not a fan of this syntax as proposed. You're using the same
keyword to mean two different but very very close things. That's very
confusing. It also means that you cannot take a global by value in a
closure.

Earlier the following was proposed:

function foo($a, &$b) global ($c, &$d) {

}

$bar = new function($a, &$b) use ($c, &$d) global ($e, &$f) {

};

Which I think is much more self-explanatory, accomplishes the same goal, and
still does not introduce any new keywords. (I still think "lexical" is
better than "use", and safe, but whatev. <g>)

--
Larry Garfield
larry@garfieldtech.com

Hi,

Attached are the patches that allow the "use" statement that was
introduced with closures to appear within every function statement
except method definitions. I think this feature is a good addition
because it resolves inconsistency between closures and unticked
functions. In a nutshell,

I talked to Johannes, given that the thread has not garned much
attention (maybe with this reply this will change) and the fact that
since quite some time we have instead tried to encourage people to
leverage $GLOBALS instead, it does not seem like we need to squeeze
this new syntax into 5.3 so shortly before the feature freeze (I guess
you get what you deserve by allowing closures in so late before the
feature freeze?).

If we get feedback that end users that are new to PHP feel like they
expect this syntax when they are exposed to closures we might want to
add this in 5.4/6.0?

regards,
Lukas Kahwe Smith
mls@pooteeweet.org

I would like to keep this as a RFC page in wiki.php.net. Are there
any conventions or rules that I should keep in mind? (or just-not-
supposed-to-do-that-because-your-proposal-is-stupid-and-will-never-be-
accepted?)

Moriyoshi

Hi,

Attached are the patches that allow the "use" statement that was
introduced with closures to appear within every function statement
except method definitions. I think this feature is a good addition
because it resolves inconsistency between closures and unticked
functions. In a nutshell,

<?php
function foo() use (&$some_globals) {
echo $some_globals;
}
?>

is equivalent to

<?php
function foo() {
global $some_globals;
echo $some_globals;
}
?>

While,

<?php
function bar() {
$some_local_var = '';
function fubar() use (&$some_local_var) {
echo $some_local_var;
}
}
?>

and

<?php
function bar() {
function fubar() {
global $some_local_var;
echo $some_local_var;
}
}
?>

are of course not the same.<php-ubiquitous-use-statement- HEAD-20080718.patch.diff.txt><php-ubiquitous-use-statement- PHP_5.3-20080718.patch.diff.txt>
Moriyoshi