Re: Attributes/Annotations Case Study: Drupal
| From: | Rowan Collins | Date: | Thu, 05 May 2016 10:34:09 +0000 |
| Subject: | Re: Attributes/Annotations Case Study: Drupal | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-93086@lists.php.net to get a copy of this message | ||
Stanislav Malyshev wrote on 05/05/2016 07:48:
I tend to agree - what the proposal basically says is "here's a generic parser, invent a domain-specific language using that parser". Theoretically, people could implement all sorts of weird "operator overloading" behaviour: <<Push($foo >> Translator)>> <<Pipe($foo|lower|escape)>> <<Query($foo ?? '//item[id=42]')>> Do we really need or want that kind of flexibility, just to avoid agreeing a specific structure for metadata? Regards, Rowan Collins [IMSoP]The key idea of RFC was not to invite another language for meta-data,but use PHP language itself. This is a good way to avoid handling a lot of issue, but what I am afraid of is that with this solution, what would happen that people start doing exactly that - inventing another languages for metadata.