On Oct 15, 2009, at 12:00 PM, Keren Lasker wrote:
There was an email about it on the list (the name changed IMP_IMPLEMENTATION_CHECK to IMP_INTERNAL_CHECK on Ben's suggestion).fine,but since this change effects more or less every file in IMP it would be nice to get an email just noting this change and not wait for IMP this week.
More to the point, I think just looking in the change history is better since you can actually do that when you do an update (rather than search through the emails on the list to try to figure out which are relevant changes and occurred since you last updated).
Also - to my understanding there are now IMP_INTERNAL_CHECK, IMP_USAGE_CHECK etc ...They are described in the docs on the macros and a bit in the intro to error checking (where the macros are documented). That page is linked from the introduction (and of course the related functions/types). However, it is not listed in the related pages list and it might be important enough to be put there (and definitely should be linked from the developers' manual).Is there some documentation on when to use what ??
--Daniel
thanks, Keren. On Oct 15, 2009, at 11:54 AM, Daniel Russel wrote:As a general comment, always take a look at the change history when you update IMP since it will include mention of such breaking changes. You can just read kernel/doc/history.dox if you don't want to build the docs.On Oct 15, 2009, at 11:48 AM, Keren Lasker wrote:did it go away ?name changed, following the email exchange.what should I use instead ??IMP_INTERNAL_CHECK (and IMP_USAGE_CHECK for IMP_check). _______________________________________________ IMP-dev mailing list https://salilab.org/mailman/listinfo/imp-dev_______________________________________________ IMP-dev mailing list https://salilab.org/mailman/listinfo/imp-dev