I think that's a stretch here. Aspect-oriented programming has the property of adding certain pre-and-post functions to certain functions (and/or identifiers) based on their names, at least from my understanding. What you would end up with, then, is code that is much harder to debug, as spelling somehow now conveys semantics. Though some might think looping through keys (above) isn't elegant enough, I still think it's better than playing aspect oriented games with the symbol table/reflection/whatever-your-language-calls-it.
| [reply] |
You are of course absolutely right, especially if one isn't lazy enough to get a return from such OO extensions .. but it was intended simply in the spirit of tmt1wtdi - and as a knowledge share.
It seems sad to me that the lead in AOP technique and standards is being driven by the large IDE players, JBoss et al.
That said, I continue to generate 90% of my OO module structure & stubs from templates and XML through my own home-rolled smoke screens ..
the 'qif;
| [reply] |