On May 9, 2007, at 23:44 , Timothy Clemans wrote:
> I was just trying to make something that would spot issues before an > object is created. You know be robust. I know what you are after, but I am not sure this is the way to do it. You can spend a long time writing code that tries to predict all the ways a user can screw things up, and you will always end up with code that is full of those kind of holes, and which rapidly becomes unmaintainable. Maybe better to approach robustness a different way (e.g., by catching errors when they happen, with 'try' clauses). I think this thread is way OT now... Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Enhancement of the Director's Income -------- When LuteFisk is outlawed, Only outlaws will have LuteFisk -------- --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
