tag:blogger.com,1999:blog-3198935374994345981.post2783340079004795671..comments2008-12-05T08:25:02.580+01:00Torkel Ödegaardnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3198935374994345981.post-52484313928115202842008-12-05T08:25:00.000+01:002008-12-05T08:25:00.000+01:00Sure AOP might break some OOP rules, but you have to be a little pragmatic, if it can save hundreds of lines of code and make your code cleaner then that violation might be OK. At least in my book :)Torkel Ödegaardhttp://www.blogger.com/profile/08914354140151859277noreply@blogger.comtag:blogger.com,1999:blog-3198935374994345981.post-91622127811769860632008-12-04T21:39:00.000+01:002008-12-04T21:39:00.000+01:00This is my view on this matter:<BR/>http://rogeralsing.com/2008/01/08/code-mangling-aop-vs-runtime-proxy-aop/<BR/><BR/>I can not see why on earth people would want AOP to break the most fundamental rules.<BR/><BR/>Eg, if you are only allowed to change the behaviour of virtual methods via OOP.<BR/><BR/>Then why should you be allowed to do so using AOP?<BR/><BR/>AOP needs to conform to the OOP rules or we will end up with all sorts of problems.<BR/><BR/>Just my 2 cents atleast..Roger Alsinghttp://www.rogeralsing.comnoreply@blogger.com