> From the collisions point of view `class` and `__CLASS__` are equally > safe.
> Imho ClassName::class reads nicer and also looks similar to the > similar ClassName.class syntax in Java. The current __CLASS__ could then be written self::class. Looks more "namespace/object oriented", where __CLASS__ feels procedural? How would static::class behave ? is it handled by the current patch? Maybe the test case could be extended to reflect this, and also for self::class? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php