Aspect oriented programming: Difference between revisions

m
sort languages, remove some fluff
m (Looks like a draft task)
m (sort languages, remove some fluff)
Line 1:
{{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.
 
Line 21 ⟶ 20:
;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.
 
=={{header|Java}}==
 
Java has an aspect oriented programming library called AspectJ. Aspects can create entry and exit intercepts on normal methods. In aspect language, features are called cross-cutting concerns.
 
=={{header|C}}==
Line 107 ⟶ 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.
 
=={{header|Java}}==
 
Java has an aspect oriented programming library called AspectJ. Aspects can create entry and exit intercepts on normal methods. In aspect language, features are called cross-cutting concerns.
 
=={{header|JavaScript}}==
Line 113 ⟶ 112:
 
=={{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!
Anonymous user