On 12 Oct 2014, at 11:36, Zeev Suraski <z...@zend.com> wrote: > For the record, I don't feel strongly about # comments, but I do think that > we should have good reasons to actually *remove* features that are better > than "this is how it's done". Valid reasons can be performance penalties of > keeping the feature, security issues, or potential significant reduction in > codebase complexity. I'm not sure whether # comments fall into any of these > buckets, but sounds like they don’t.
Allowing # for comments stops you from using # in string property values. Though I’m not sure why you’d need to. -- Andrea Faulds http://ajf.me/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
