Anonymous user
Talk:Aspect oriented programming: Difference between revisions
Agreed; page focus is all skewed and very unclear
m (→Comment on the task as it stands: Link.) |
(Agreed; page focus is all skewed and very unclear) |
||
Line 12:
::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)
::: Indeed. You can't implement a feature (well, you can but it's usually a lot more work than you want to show on a webpage) but you can deal with a specific task. More to the point, you can ''compare'' task solutions across languages much more easily as well, and it is the comparisons that this site really lives for. (If anyone goes to the effort of making this an actual task, please mark this as {{tmpl|draft task}} or {{tmpl|task}} please so that it pops up on my list of things to implement!) –[[User:Dkf|Donal Fellows]] 11:10, 13 October 2011 (UTC)
==Comment on the task as it stands==
| |||