problem about aspect-oriented-Collection of common programming errors
mgroves
compiler aop aspect-oriented
I’m doing a presentation about Aspect Oriented Software Development. One of my subtopics is “AO Compiler: weaving process”. I found nothing about it on the internet. Does anybody have some information about this Compiler? I really don’t know what to write about it.(I don’t want you to do my work, I just need some help at the beginning!)Here is a similiar question: AspectJ Weaving, but unfortunalety it doesn’t have any answers yet.
soc
java methods annotations aspectj aspect-oriented
I’d like to match a method like this:@Foo public void boo(@Baz Bar bar) { … }Basically:the method has a @Foo annotation (which I match with execution(@Foo * *(..)) && @annotation(foo)), can have a variable amount of parameters, and one of them should have a @Baz annotation, I need to further work with that annotated argument (bar).If a method has a @Foo annotation but is missing a @Baz annotation, I want to get an error as early as possible, if possible when weaving and not at runtime.
Lawrence Wagerfield
c# .net aop postsharp aspect-oriented
Before I start, I’d like to clarify that my current understanding of AOP terminology is as follows…Aspects are the AOP equivalent of Classes in OOP. Advices are the AOP equivalent of Methods in OOP. Pointcuts are the AOP equivalent of ‘using’ code in OOP. In OOP we invoke things. In AOP we weave things. The decision of what to weave where is defined by Pointcuts.Onto the actual question…I have a logging aspect in PostSharp which I want to use (weave) on every method, excluding properties. Or
DMKE
actionscript-3 frameworks aop aspect-oriented
I’m looking for a full featured AOP Library for Actionscript 3.The following projects I noticed so far, but they all seem to have their problems:http://farmcode.org/page/Sodality.aspx looks most promising so far, however it requires you to create a whole new class for every AOP “call” I believe, and it forces you to follow quite a lot of restrictions, anyone has experience with it? http://code.google.com/p/loom-as3/ this one is discontinued http://code.google.com/p/floxy/ dynamic proxy generatio
Tom Wijsman
paradigms aspect-oriented
Aspect oriented programming promises to deal with cross cutting concerns, but I’m not completely sold on it yet. Have there been any other attempts to deal with this problem?
glenviewjeff
development-methodologies aspect-oriented
From everything I have learned about “Aspect-Oriented Programming” or “Aspect-Oriented Software Development,” labeling it as a programming paradigm or methodology appears to be inaccurate. From what I can tell it is not a fundamental technique for programming. To nail down what is meant by “paradigm” and “methodology,” please refer to the following definitions from the American Heritage Dictionary. Compare how well or poorly “Object-Oriented Programming” applies to each vs. how well AOP fits.
Akim
c# reflection dependency-injection postsharp aspect-oriented
I have designed couple of aspects using PostSharp for different projects, but there is a design flaw in many of them: dependency management.This is a question about injection of dependencies into aspects, not about dependency injection using aspectsDue to nature of PostSharp post-compilation there are several limitations applied to aspectsConstructor injection is not applicable. Constructor will be executed once during post-compilation, then object will be serialized and later deserialized multi
Warren Seine
c++ macros aspect-oriented
I hate macros. I’m trying to avoid using them as much as I can, but I occasionally need them to enable / disable features in my code. Typically:#ifdef THREAD_SAFEtypedef boost::mutex Mutex;typedef boost::mutex::scoped_lock ScopedLock; #elsetypedef struct M { } Mutex;typedef struct S { S(M m) { } } ScopedLock; #endifThis way I can leave my actual code unchanged. I’m trusting the compiler to remove the placebo code when the macro is undefined.I’m aware that template specialization could
Web site is in building