Tuesday, May 22. 2007
 |
 |
 |
 |
Posted by Stephan Schmidt
in
Planet PHP, Tutorials Comments (4) Trackback (1) |
 |
 |
 |
 |
Declarative Development Using Annotations
Today, Frank and I did a session about annotations in PHP at the International PHP Conference 2007 - Spring edition. The slides give you an overview, how annotations are used in Stubbles and how you can leverage them in your own application.
A PDF version of the slides is also available on the Stubbles download page.
A PDF version of the slides is also available on the Stubbles download page.
Comments
Display comments as
(Linear | Threaded)
Hey Stephan,
I liked your presentation, and the 'inline asserts' was an eyeopener. Makes writing tests for simple methods a lot easier, thus it will be easier to convince developers to actually do unit testing.
I have some doubts about the other usages though, such as the xml, db and csv examples that you had. In one of the first slides you listed the basic rule that an annotation is an annotation, meaning that it should not alter the code in any way. What is really meant by that paradigma is that if you remove the annotations, the app should still work. The examples you demonstrated violate that principle.
But for documentation purposes and additional tooling, it's a great idea.
I liked your presentation, and the 'inline asserts' was an eyeopener. Makes writing tests for simple methods a lot easier, thus it will be easier to convince developers to actually do unit testing.
I have some doubts about the other usages though, such as the xml, db and csv examples that you had. In one of the first slides you listed the basic rule that an annotation is an annotation, meaning that it should not alter the code in any way. What is really meant by that paradigma is that if you remove the annotations, the app should still work. The examples you demonstrated violate that principle.
But for documentation purposes and additional tooling, it's a great idea.
I think you misconceived the rule that an annotation does not alter the code. The rule is true for the code that the annotation is annotated to, but it does not apply to code that uses the annotations to do a specific task.
Actually, it does. That's why it's called an annotation.
The rule would not make sense if it only applied to the code it annotates, if the app as a whole is affected by it's absence.
The rule would not make sense if it only applied to the code it annotates, if the app as a whole is affected by it's absence.
Then I guess a whole bunch of people got it wrong...
http://java.sun.com/developer/technicalArticles/J2SE/constraints/annotations.html
http://www.hibernate.org/hib_docs/annotations/reference/en/html/entity.html
http://www.osoa.org/display/PHP/SCA+with+PHP
http://java.sun.com/developer/technicalArticles/J2SE/constraints/annotations.html
http://www.hibernate.org/hib_docs/annotations/reference/en/html/entity.html
http://www.osoa.org/display/PHP/SCA+with+PHP
Calendar
|
October '08 | |||||
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||
Categories
Quicksearch
Blogs we read...
Syndicate This Blog
Blog Administration
This week I was at the International PHP Conference. It was a nice conference with interesting topics. It was however a bit of a pity that the PHP conference got 'cornered' by the Webinale conference, which was a lot bigger and caused the PHP sessions to
Tracked: May 25, 20:40