Anonymous user
Talk:Aspect oriented programming: Difference between revisions
no edit summary
(identify features of aspect oriented programming that the language supports) |
No edit summary |
||
Line 9:
:Maybe the task is to identify features of aspect oriented programming that the language supports. We probably don't need any specific application in mind. There are a variety of methods mentioned in the task description, so implementers could probably use that as a guideline --[[User:Markhobley|Markhobley]] 16:13, 10 June 2011 (UTC)
::a generic description of features is surely useful, but for language comparison a more specific problem would be nice. it would enable implementers to demonstrate alternative ways to solve the problem if the language does not support aspect oriented programming directly.
::a possible task could be: you have a library whose source you can not change, and you want to print a trace of the function execution that happens in the library. the task is to print each function call and its arguments before they are happening. (a backtrace that may be provided by the language is not acceptable)
::this task is i believe suitable for aspect oriented programming as it requires to intercept the function calls without changing the code in the functions. however implementers are free to take advantage of any language feature to solve the problem, thus allowing the reader to not only learn about aspect oriented programming features but also find out how the problem can be solved if the language does not support aspects directly.--[[User:EMBee|eMBee]] 02:27, 13 October 2011 (UTC)
| |||