commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Graham" <>
Subject Re: chop/chomp/slice - how to deprecate?
Date Mon, 17 Mar 2003 15:51:04 GMT
Usually you deprecate the existing method and replace its functionality to a 
call to the new method.


>From: Alex Chaffee / Purple Technology <>
>To: Jakarta Commons Developers List <>
>Subject: chop/chomp/slice - how to deprecate?
>Date: Mon, 17 Mar 2003 07:44:56 -0800
>I've made a first pass at reworking chop and chomp, so that:
>* chop works like perl (always remove last character)
>* chomp works like perl (remove last character only if it's a newline)
>* chopNewline is deprecated with a message "use chomp instead"
>* all the previously named "chomp" functions are renamed "slice":
>	slice, slicelast, getslice, preslice, getpreslice
>Henri, is this an acceptable name change?
>Before I check it in, I'd like some consensus on the deprecation
>strategy.  We've renamed some methods, and also changed the behavior
>of an existing method -- slighly, but significantly.
>Do we...
>* Check it all in as is, and just make sure to document the changes in
>the readme for the next release?
>* Put in stub implementations for the old chomp* functions and mark
>them with a @deprecated tag?
>* Contact anyone who's using them -- I'm thinking about Gump, and its
>concept of dependencies between Jakarta projects -- If so, how would
>we locate all these users?
>If anyone wants to see my changes, let me know and I'll send you a
>patch file.
>Alex Chaffee                     
>Purple Technology - Code and Consulting
>jGuru - Java News and FAQs       
>Gamelan - the Original Java site 
>Stinky - Art and Angst           
>To unsubscribe, e-mail:
>For additional commands, e-mail:

The new MSN 8: smart spam protection and 2 months FREE*

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message