Dear all,
> Now I stand behind this 100% doctest policy!
Thank you all for your very helpful comments! They encouraged me to do
the effort and provide examples for the tiniest bit.
Particularly convincing is for me that, although so far my code works
stable under Linux on various machines, there might be high-level doc-
test failures on a different machine -- and then bug hunting is no
fun.
Follow up question: What is a *good* doc test for a basic method?
Perhaps the question is ill-posed. Therefore an example: If I have a
__dealloc__ method for an extension class, is it really a sufficient
doc test to construct an instance of that class and then to delete
it?
Hmm, probably yes: If the __dealloc__ does not work properly then
either there is a segfault (due to a double free, for example), or a
leak that might be detected by valgrind or other tools.
Cheers
Simon
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
