Do you know Aspect Oriented Programming?
Is it good or bad do you think?
Aspect Oriented Programming
Do you know Aspect Oriented Programming?
Is it good or bad do you think?
Just GET it OFF out my mind!!
News to me. But what prompted such a question? Is any programming paradigm bad based on anything but preferences? I don't think so.
I'd never heard of it before, but WikiPedia gave me some idea what it is about. It sounds like an interesting concept. Will it take over the world? Probably not in the next couple of years, I'd hazard a guess....
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
Phew...
Just GET it OFF out my mind!!
Its more an addition to your toolbox rather then a single way of programming.
I've experimented a bit with it a couple months ago and found it usefull to do logging for example. Instead of having to rewrite all my server side (i was using java rmi) methods in order to log everything that was happening I could just insert bits of code by using the aspect oriented approach.
The only drawback is that if you overdo the amount of aspect oriented programming it just gets alot more difficult to debug... But for tasks such as logging or even authentication perhaps it can be very usefull.
Last edited by GanglyLamb; 05-23-2009 at 07:19 AM. Reason: 10 more posts and i reach the epic number 1111
Originally Posted by Salem
Another miss understanding due to practical tools...
Just GET it OFF out my mind!!
I haven't seen the implementation without the use of actual compile time tools for C# and java. I am aware that there is a school of thought that programs in this way but from whatI saw of it it seems like a crutch to avoid refactoring legacy code or making it so you can create aspects without the use of tools.
Also in the TDD environment it's almost impossible to unit test.
