On Sat, 2004-03-06 at 15:53, Timm Friebe wrote:
[...]
> I'm not sure whether this affects a lot of users, and as noone has
> commented on it, I guess PHP5 will get away with this break:)
>
> I'll just have to find a workaround if you insist the PHP4 behaviour is
> broken:)
Additionally, it should be mentioned in README.PHP4-TO-PHP5-THIN-CHANGES
- Timm
Index: README.PHP4-TO-PHP5-THIN-CHANGES
===================================================================
RCS file: /repository/php-src/README.PHP4-TO-PHP5-THIN-CHANGES,v
retrieving revision 1.15
diff -u -r1.15 README.PHP4-TO-PHP5-THIN-CHANGES
--- README.PHP4-TO-PHP5-THIN-CHANGES 12 Feb 2004 14:44:58 -0000 1.15
+++ README.PHP4-TO-PHP5-THIN-CHANGES 6 Mar 2004 18:42:43 -0000
@@ -68,3 +68,13 @@
will be a fatal error like :
Fatal error: Class 'fubar' not found in ....
If there is defined function __autoload() it will be called.
+
+9. An object with no properties is no longer considered "empty".
+ <?php
+ class test { }
+ $t= new test();
+ var_dump(empty($t)); // Will echo bool(false)
+ if (!$t) {
+ // Will be executed
+ }
+ ?>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
