Fri, 1 Nov 2002 09:21:44 +1300
I actually quite like the semantics, it may not be terse but it's much
easier to read and figure out what is going on.
If we have to delete it I would favour deprecating it for a while,
especially if it actually works.
Just my $0.02
> -----Original Message-----
> From: Thomas Down [mailto:firstname.lastname@example.org]
> Sent: Friday, 1 November 2002 4:14 a.m.
> To: email@example.com
> Subject: [Biojava-l] FeatureFilter.AndNot
> Posting this to biojava-l rather than biojava-dev, to get
> maximum visibility...
> Does anyone use the FeatureFilter.AndNot class anywhere?
> This is redundant in that:
> new FeatureFilter.AndNot(foo, bar)
> Could be expressed as:
> new FeatureFilter.And(foo, new FeatureFilter.Not(bar));
> It's really a leftover from an old attempt to provide
> a general-purpose optimization framework for the
> FeatureFilter language. Since that was never completed, this
> class appears to be cruft, and it now just interferes with
> the more recent FeatureFilter optimization strategies which
> ARE being actively used.
> So... has anyone, anywhere, actually written code which
> relies on this? If I don't here anything by tommorow, it'll
> be gone in 1.3.
> Biojava-l mailing list - Biojavafirstname.lastname@example.org
Attention: The information contained in this message and/or attachments
from AgResearch Limited is intended only for the persons or entities
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipients is prohibited by AgResearch
Limited. If you have received this message in error, please notify the