On Mon, 3 Mar 2003 23:52, Berin Loritsch wrote: > Peter, you have been presented many opportunities to present your use > cases.
I prefer to only add code that has a use case. If no valid use case can be provided don't add it. No valid use case has been provided so why add the complexity? > Also, you need to think of our users. If a method is introduced in > one release, and then deprecated in the next--with no clear technical > advantage--then they will start to get fed up with our stuff. I > personally don't want to see that happen. yer - much better to put shit code out and then in a few years start removing it and deprecating it once they have dependencies on it. Thats the way the rest of the code evolved so lets keep helping our users this way. -- Cheers, Peter Donald *-------------------------------------------------* | An eye for eye only ends up making the whole | | world blind. - Gandhi | *-------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
