Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 1671 invoked from network); 16 Jul 2003 01:52:23 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 16 Jul 2003 01:52:23 -0000 Received: (qmail 24498 invoked by uid 97); 16 Jul 2003 01:55:00 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org Received: (qmail 24491 invoked from network); 16 Jul 2003 01:54:59 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 16 Jul 2003 01:54:59 -0000 Received: (qmail 1372 invoked by uid 500); 16 Jul 2003 01:52:21 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 1357 invoked from network); 16 Jul 2003 01:52:20 -0000 Received: from unknown (HELO atlanta.seagullsw.com) (12.6.96.143) by daedalus.apache.org with SMTP; 16 Jul 2003 01:52:20 -0000 Received: by mail.seagullsw.com with Internet Mail Service (5.5.2656.59) id <30SCPRV3>; Tue, 15 Jul 2003 21:52:27 -0400 Message-ID: <245A7290F0E0D311BF6E009027E7908B072046A2@mail.seagullsw.com> From: Gary Gregory To: 'Jakarta Commons Developers List' Subject: RE: [lang] StringUtils isEmpty - deprecate or change? Date: Tue, 15 Jul 2003 21:52:26 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34B3C.E89A67A0" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C34B3C.E89A67A0 Content-Type: text/plain I am +1 on #2. I am +1 on the #3 idea but not as a subclass. IF we really wanted something like this, why not then create a String wrapper class which behaves and looks more OO. Another discussion I know... ;-) Gary -----Original Message----- From: Stephen Colebourne [mailto:scolebourne@btopenworld.com] Sent: Tuesday, July 15, 2003 17:11 To: Jakarta Commons Developers List Subject: [lang] StringUtils isEmpty - deprecate or change? Please keep this thread focussed on deprecation or not. For the 2.0 release, the chomp() methods have already changed functionality to be closer to Perl. Other methods have had null handling changed to be silent rather than NPE. Proposals are to change isEmpty() and isNotEmpty() functionality. Choices are 1) Use a different method name and deprecate original. Virtually impossible as method names are critical. 2) Change the functionality and document as with chomp(). This is a major version release, so this seems fair. 3) Create a new class StringTests to hold all the isXxx() methods from StringUtils. Deprecate the original methods, pointing at StringTests. (Side advantage, decreases size of StringUtils) (Side disadvantage, increases API) It would be possible for StringUtils to extend StringTests for minimum impact. Personally, I choose #2. That is what a major version is for. Particularly this version 2 which is ironing out issues like this. Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org ------_=_NextPart_001_01C34B3C.E89A67A0--