| <?php | |
| class A{ | |
| protected $b; | |
| function __construct() {unset($this->b);} | |
| function __get($name){ | |
| echo $name; | |
| return $this->$name; | |
| } | |
| } | |
| $a = new A; |
This release has two major improvements. The first one is that react/dns is now using a promise based API. In case you missed it, react/promise is a PHP library for promises. Take a look at the README and familiarize yourself with it, as it will be used by many libs in the react ecosystem, including core.
The previous API was:
$dns->resolve('igor.io', function ($ip) {
echo "Yay, the IP is $ip.\n";
| <?php | |
| $factorial = call_user_func( | |
| function ($le) { | |
| return call_user_func( | |
| function ($f) { | |
| return $f($f); | |
| }, | |
| function ($f) use ($le) { | |
| return $le(function ($x) use ($f) { |
This is just a small post in response to [this tweet][tweet] by Julien Pauli (who by the way is the release manager for PHP 5.5). In the tweet he claims that objects use more memory than arrays in PHP. Even though it can be like that, it's not true in most cases. (Note: This only applies to PHP 5.4 or newer.)
The reason why it's easy to assume that objects are larger than arrays is because objects can be seen as an array of properties and a bit of additional information (like the class it belongs to). And as array + additional info > array it obviously follows that objects are larger. The thing is that in most cases PHP can optimize the array part of it away. So how does that work?
The key here is that objects usually have a predefined set of keys, whereas arrays don't:
| <?php | |
| class Foo | |
| { | |
| protected $foo; | |
| protected $bar; | |
| protected $baz; | |
| } |
| <?php | |
| // thanks to metaultralurker on reddit for inspiration | |
| function map(callable $fn, \Traversable $data) { | |
| foreach ($data as $v) { | |
| yield $fn($v); | |
| } | |
| } |
A few notes from my personal gripes about what InputFilter is and does.
InputFilter is a terrible name as the class mixes sanitation and validation. Rename to something far more appropriate (e.g. InputManager?).setData()For example, if both raw and sanitized data are required: