[Bioperl-l] Feature/Annotation rollback(update)

Hilmar Lapp hlapp at gmx.net
Sun Aug 26 00:58:46 EDT 2007


The reason was to provide for backward compatibility with the  
original API in which tag values were scalars, not objects. The idea  
was that if someone relied on that and treats the object as a scalar  
(comparison, printing, etc), the operator overloading would take care  
of that.

So by going back to the original API the overloading should become  
obsolete, at least theoretically.

The overloading can cause some very subtle issues that I pointed out  
in an earlier email. It's one of those really "clever" tricks that  
just make it very hard for newcomers to understand what's going on in  
their code.

	-hilmar

On Aug 25, 2007, at 6:12 PM, Chris Fields wrote:

> I have finished rolling back most of the specific changes made prior
> to the 1.5 release and have relevant tests passing:
>
> http://www.bioperl.org/wiki/Feature_Annotation_rollback#First_round
>
> Operator overloading of Bio::Annotation objects will be trickier to
> debug as tons of tests fail when the overloading is removed:
>
> http://www.bioperl.org/wiki/Feature_Annotation_rollback#Second_round
>
> I'll start looking into fixes.  I don't like overloads from a
> personal standpoint (problems w/ long-term code maintenance), but was
> there a more specific reason for removing them?
>
> chris
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/bioperl-l

-- 
===========================================================
: Hilmar Lapp  -:-  Durham, NC  -:-  hlapp at gmx dot net :
===========================================================







More information about the Bioperl-l mailing list