Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
are monads, or more specifically f# computational expressions, a form of aspect oriented programming?
Update:
f# workflow builders have methods other than bind and unit. They have hooks for lots of keywords. see Creating a New Type of Computation Expression.
To the extent that monads serve to isolate a generalized computation strategy from the specifics of its algorithm or implementation, they can be seen as a basis or theoretical foundation for AOP. I found an interesting paper called Monads as a theoretical foundation for AOP (PDF) that gives this idea a more thorough treatment.
for me it somewhat feels a bit like AOP. Classic example in my work is using a "log-Workflow" (better known as a state-monad with the state beeing a log-entry) for loging inside my F#-code to spare me from passing the log-object through every method-call. On the other hand "real" AOP doesn't need you to write log-code inside your methods at all (maybe some attributes). I don't like the "hey I rewrite your code for you"-AOP frameworks so I just use Unity-Injection from time to time (yes I really use Unity - does everything I want from it) and it's ok.
