There's been slowly building hype about aspect oriented programming (AOP) for
about 10 years, and it is very interesting and will add efficiencies to
software development. The example I always come across when looking into it
is the error/exception handling issue: this is an example of a duplication of
concept that AOP seeks to centralize.
*But*, it's not meant to replace OO, it is an additional concept that will
address some things that OO alone cannot address. OO is actually more
all-encompassing in what it addresses than AOP.
Ultimately though, the whole point of OOP, AOP, extreme programming, and
most of the grizzled old programmer wisdom out there is mainly about one
thing: "reduce duplication of logic and knowledge". If you can limit the
number of places in your code where certain information has to be understood
by someone maintaining it to "just one place", then you have already achieved
most of the benefits of AOP to ZOP. AOP to ZOP are all just ways of imposing
structures on programmers that tend to lead to (but not force) the "just one
place" philosophy.
--
David Anton
www.tangiblesoftwaresolutions.com
Home of:
Clear VB: Cleans up outdated VB.NET code
Instant C#: Converts from VB.NET to C#
Instant VB: Converts from C# to VB.NET
Instant J#: Converts from VB.NET to J#
"ma*********@yahoo.co.in" wrote:
Hi all just wondering will the next hype be aspect oriented
programming.
I was reading through this link and just thought about it
http://www.geocities.com/aspectdotnet/
