Aspect oriented programming: Difference between revisions
Content added Content deleted
m (Looks like a draft task) |
m (sort languages, remove some fluff) |
||
Line 1: | Line 1: | ||
{{draft task}} |
{{draft task}} |
||
;Background |
|||
The main goal of Aspect Oriented Programming (AOP) is to keep all the code relating to a single feature in one module of code. |
The main goal of Aspect Oriented Programming (AOP) is to keep all the code relating to a single feature in one module of code. |
||
Line 21: | Line 20: | ||
;Task |
;Task |
||
The task is to describe or show how, or to what extent, a given programming language implements, or is able to implement or simulate, Aspect Oriented Programming. |
The task is to describe or show how, or to what extent, a given programming language implements, or is able to implement or simulate, Aspect Oriented Programming. |
||
⚫ | |||
⚫ | |||
=={{header|C}}== |
=={{header|C}}== |
||
Line 107: | Line 102: | ||
In as much as I am unable to see the differences between functional programming and aspect oriented programming (they are just that stealthy, from my point of view), I'll have to say that J is as aspect oriented as the capabilities of the programmer. |
In as much as I am unable to see the differences between functional programming and aspect oriented programming (they are just that stealthy, from my point of view), I'll have to say that J is as aspect oriented as the capabilities of the programmer. |
||
⚫ | |||
⚫ | |||
=={{header|JavaScript}}== |
=={{header|JavaScript}}== |
||
Line 113: | Line 112: | ||
=={{header|Scala}}== |
=={{header|Scala}}== |
||
==New Page Notes== |
|||
I may have described a feature-oriented programming paradigm, or something related to modular programming. If so please feel free to rename or refactor the page! |