NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Donald E. Knuth
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Re: Aspect 0.90 - Aspect-Oriented Programming... (Score:1)
Adam, this is cool.
However, I'd be interested in the nature and details of your never-heard-of billion dollar site stability work. Any chance of you talking about that?
Tiny nit (Score:1)
I should file this as a bug or fix it in SVN myself, but there's a small typo in the synopsis of 0.90: s/\$wormhole/\$aspect/
Some issues with AOP (Score:2)
One thing I think you should note in your documentation is that it's very important to realize that a software must not rely on aspects to function. That is to say, if all pointcuts fail to match, the software must still be correct. Aspects should generally add behaviour, not alter it.
For example, one common example Java programmers use is to mark code as thread-safe. However, if a pointcut fails to match a function which must be thread-safe, the match fails silently. As a result, previously thread-safe co
Re: (Score:2)
I concur.
I think while AOP shows promise for stuff beyond just tracing, logging and what not, I can't see how you could scale it without similar problems to many other purely declarative systems like XSLT where actions happen in parallel and at a distance.
I'll look at adding some kind of Aspect Caveats section to the documentation.
Bitwise operators? (Score:1)
Hey, what's with the bitwise operators? Would ordinary boolean operators work here or are you doing this for some invisible-to-me precedence reason?
Re: (Score:2)
Historical reasons.
The bitwise operators were the ones that the Aspect library used when I took it over.