Keren Lasker wrote: > What does it mean ?

Any class that currently says "this class is deprecated" when you use it will in future not work at all, because it won't exist. ;)

This is fine with me - it will clean up the documentation and it should still be clear to everybody which classes to use to replace the deprecated ones. I can certainly anybody whose code breaks as a result.

Ben

To save other people the trouble of digging it up, here is the prior announcement. ------------------------------------------------------------------------ There are a number of classes in IMP.core which have been marked as deprecated for a while. I would be good to get rid of them entirely before the first public release. I propose that after the first marked stable version (a concept which will be explained in a forthcoming email from Ben), I remove them from SVN. So please check your code to make sure you don't use them and if you do, start migrating to the replacement classes. You can find a list of such classes at https://salilab.org/imp/doc/doxygen/deprecated.html and you code should spit out warning messages whenever you create an instance of such a class. ------------------------------------------------------------------------

That said, I just noticed that several of the classes on the deprecated list don't spit out warnings. Not sure that anyone actually looked at the warnings anyway :-) I'll add warnings to the remaining classes.

Keren Lasker wrote: > What does it mean ? > > > > > On Feb 5, 2009, at 2:02 PM, Daniel Russel drussel@gmail.com wrote: > >> Since we now have a recent Ben Blessed Branch (aka stable branch), >> I'd like to remove the deprecated classes from core. Last chance to >> squawk. >> --Daniel >> _______________________________________________ >> IMP-dev mailing list >> IMP-dev@salilab.org >> https://salilab.org/mailman/listinfo/imp-dev > _______________________________________________ > IMP-dev mailing list > IMP-dev@salilab.org > https://salilab.org/mailman/listinfo/imp-dev