rfc:annotations

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rfc:annotations [2011/05/10 03:19]
pierrick
rfc:annotations [2017/09/22 13:28] (current)
Line 4: Line 4:
   * Date: 2010-08-24   * Date: 2010-08-24
   * Author: Guilherme Blanco <​guilhermeblanco@hotmail.com>,​ Pierrick Charron <​pierrick@php.net>​   * Author: Guilherme Blanco <​guilhermeblanco@hotmail.com>,​ Pierrick Charron <​pierrick@php.net>​
-  * Status: ​Ready for discussion+  * Status: ​Declined
   * First Published at: http://​wiki.php.net/​rfc/​annotations   * First Published at: http://​wiki.php.net/​rfc/​annotations
  
Line 18: Line 18:
   * **Doctrine** For Object-Relational mapping, examples: @Entity, @OneToOne, @Id, etc.   * **Doctrine** For Object-Relational mapping, examples: @Entity, @OneToOne, @Id, etc.
   * **Zend Framework Server classes** Used to automate mappings for XML-RPC, SOAP, etc.   * **Zend Framework Server classes** Used to automate mappings for XML-RPC, SOAP, etc.
-  * **FLOW3** for dependency injection and validation+  * **TYPO3** for dependency injection and validation
   * **Symfony2** for routing rules   * **Symfony2** for routing rules
   * **Others** One clear thing that comes to my mind is Validation, Functional Behavior injection (which could take advantage of [[rfc:​Traits]]),​ etc. Also, any Framework could take advantage of it somehow.   * **Others** One clear thing that comes to my mind is Validation, Functional Behavior injection (which could take advantage of [[rfc:​Traits]]),​ etc. Also, any Framework could take advantage of it somehow.
rfc/annotations.1304997543.txt.gz · Last modified: 2017/09/22 13:28 (external edit)