Re: [RFC] Shorter Attribute Syntax Change RFC 0.2
| From: | Andreas Leathley | Date: | Mon, 17 Aug 2020 22:42:36 +0000 |
| Subject: | Re: [RFC] Shorter Attribute Syntax Change RFC 0.2 | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-111604@lists.php.net to get a copy of this message | ||
On 18.08.20 00:03, Benas IML wrote:
And then boo-yah, 6 months later we want to implement a cool new feature to attributes (a lot of examples were said before, ain't repeating myself) but we can't :(( because there is no ending delimiter and thus, we will run into parsing issues.Both @{} and @@{} would be possible as a future extension of the syntax and would have no BC break at all, if extending the syntax is something that would/should happen - just as possible suggestions. It is likely though that the vast majority of attribute usage will be quite simple (like the ones we have today with annotations: for routes, for validation, for ORMs), so having a simple syntax for a feature which is mostly used in a straightforward way does not seem that crazy. And about your condescending remark of people trying to add to the discussion who have not "proven themselves in the PHP source code": Having a discussion with people who have different viewpoints seems like a big benefit for any project, because it is impossible to be an expert at C code, php-src, PHP code, all PHP frameworks, all the PHP libraries, and all the ways PHP is used today - yet all that can be relevant for language changes and the actual usage of new features, including the syntax.