$data = array (
'id' => $_POST["id"],
'name' => $_POST["name"],
'email' => $_POST["email"]
);
Is there a single php function that can transform the array keys into variables having the value of the array value? For instance instead of echoing a value via echo $data['name'] I can simply use echo $name.
Please do not suggest solutions using foreach loops (if possible).
extract does just this: (docs)
$size = "large";
$var_array = array("color" => "blue",
"size" => "medium",
"shape" => "sphere");
extract($var_array, EXTR_PREFIX_SAME, "wddx");
echo "$color, $size, $shape, $wddx_size\n";
list does as well, in a more controlled fashion (docs), just note that your source array must be numerically indexed - no associative arrays allowed here:
$info = array('coffee', 'brown', 'caffeine');
// Listing all the variables
list($drink, $color, $power) = $info;
echo "$drink is $color and $power makes it special.\n";
extract() seems to work. However I'm not sure if list() works with associative arrays.
extract($_POST);
http://php.net/manual/fr/function.list.php
You're maybe looking for the list function, so you know which variable you are dealing with.
list($var, $var2) = $_POST;
list is only valid for numerically indexed arrays.A foreach loop in this case is actually a pretty compact solution...
foreach ( $data as $key => $value ) { $$key = $value; }
Although, simply referencing the array by key is fairly tidy in and of itself...
echo $data['id'];
extract with a foreach loop, and how is that compact considering there is a single function call available to accomplish the same result? Normally I wouldn't downvote over this kind of inefficiency, but in this case you came 10 minutes after extract was given as an answer (by several people) to suggest longer code that does the exact same thing... pointless.extract() are of the same sort that running PHP with register_globals = On option has. That's why in my comment above, I warned against running extract() directly on GPC arrays. However, if you learn how to use extra arguments extract() takes (especially the prefix one) you can feel perfectly safe.extract() will not overwrite any of your variables, that you would not like it to (like $loggedAsAdmin or something ;) ). With the rest deal like you would with any data that comes from userland.extracted values across included files, and don't for Pete's sake make them global. Look - there's a lot of things people will tell you "NEVER DO XXX" or "XXX is harmful". "Bad practice", they scream. This is all silly. If there's a feature in a language, there is an appropriate time and way to use it. Some features, like extract, must be used with caution because they are easy to misuse. That doesn't mean they have the plague. If they were so bad as all that, they wouldn't be in the language.eval() is not evil sometimes ;P