On 12/21/06, Kent Tong <[EMAIL PROTECTED]> wrote:
4) As a result of 3), the programmer cannot explicitly express his intention to participate in the rendering phase. If later someone else modifies the code, particularly if he is not very familiar with Tapestry as Jesse pointed out, he may not know the significance of the method name and may change it to better reflect what the method does. With an annotation it is highly unlikely that he will change it when it is something that he doesn't understand.
Well i take your point but, modifying a class which interact with a framework without knowing how the framework work, seems obvious to expect unknown behavior. Don't you? -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
