On Thu 11 Sep 2008 at 08:32PM, Tom Mueller wrote:
> I disagree, but I don't think that really matters.
There is no API in anything but the most useless sense of the word.
That is to say, there is almost no stability, either in theory or
practice.
> Python provides several ways to preserve compatibility of interfaces.
> We just need to use them.
Please elaborate. Here are the problems you need to solve:
- If I'm going to delete image.do_something() and you were using that,
you're hosed.
- If I'm going to change the type of an argument, or add a new
required argument, you're hosed.
- If I'm going to change the functionality of a routine, so that it
merges two older routines together, or splits two older routines apart,
you're hosed.
- If I'm changing the class hierarchy (names, semantics, inheritance
relationships), you're (likely to be) hosed.
- If I'm changing the name or semantic function of a module, you're hosed.
Additionally, even if we had robust and performant language mechanisms
to cope with all of this, how would we test every change to ensure that
every changeset's code was backward compatible with every other
changeset?
-dp
--
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
