"TD" == Thomas Down <[EMAIL PROTECTED]> writes:
TD> On the other hand, some of the other uses of AspectJ look
TD> /very/ interesting to me. In particular, pre- and post-conditions
TD> are something which have always appealed to the paranoiac in
TD> me :-). I'll take a proper look at thi
On Thu, Dec 13, 2001 at 08:55:33AM -0800, Vladimir G Ivanovic wrote:
>
> AspectJ (http://aspectj.org) allows you to multiply inherit, provided
> there are no naming conflicts. AspectJ produces either Java bytecode or
> optionally Java source which you can then compile with your favorite
> Java co
I forgot to add that the October 2001 issue the Communications of the
ACM a dozen or so articles on aspect-oriented programming.
Here's a link to the issue's table of contents:
http://portal.acm.org/toc.cfm?id=383845&type=issue&coll=portal&dl=ACM&idx=J79&part=magazine&WantType=Magazines&ti
"TD" == Thomas Down <[EMAIL PROTECTED]> writes:
TD> A few people have asked recently about features implementing
TD> multiple Feature interfaces. In principle there's no reason not to
TD> (especially if we use code similar to the current ProjectionEngine
TD> system to dynamically generate
Hi.
My oppinion, not that it realy counts now, is that we should look at
making features mutable. The ChangeEvent system will allow us to plug in
special-case handlers for things like "child re-located outside range of
parent". I'd not be upset to see the feature.template stuff replaced by
bu
On Wed, Dec 12, 2001 at 02:17:31PM -0500, Michael Jones wrote:
> Just out of curiosity what was the design decision that led to
> Features not being Immutable and only allowing modification of
> Feature.Templates?
Hmmm, I take it you mean `not mutable'?
Well... the Feature interface hasn't
Just out of curiosity what was the design decision that led to Features not being
Immutable and only allowing modification of Feature.Templates?
___
Biojava-l mailing list - [EMAIL PROTECTED]
http://biojava.org/mailman/listinfo/biojava-l
