On Fri, 5 Dec 2003, Stephen Colebourne wrote:
The 'line' is the release. Once code is released we have a duty of backwards
compatability to it. Thats not to say it will never move, but it can only do
so by deprecating the original.
I think we should be trying harder than that.
While we may
From: Rodney Waldhoff [EMAIL PROTECTED]
On Fri, 5 Dec 2003, Stephen Colebourne wrote:
The 'line' is the release. Once code is released we have a duty of
backwards
compatability to it. Thats not to say it will never move, but it can
only do
so by deprecating the original.
I think we
On observing some of the programming activity on this list, I find that
classes are moved around -- respectably speaking, refactored -- into other
packages quite generously. I would like to know what the general guidelines
to this are, especially I mean, where do you draw the line. And with
The 'line' is the release. Once code is released we have a duty of backwards
compatability to it. Thats not to say it will never move, but it can only do
so by deprecating the original.
Some refactoring occurs because of history - collections was a bundle of
collections written elsewhere rather
