(I've switched my subscription over from digest back to full so I don't miss these).
Thanks for re-posting this. I can see that this change will not affect me; if there are any places where the difference between isEmpty() and isBlank() will affect me, my test suite should find them. -- Howard M. Lewis Ship Creator, Tapestry: Java Web Components http://jakarta.apache.org/tapestry > -----Original Message----- > From: Stephen Colebourne [mailto:[EMAIL PROTECTED] > Sent: Friday, July 18, 2003 6:33 PM > To: Jakarta Commons Developers List > Subject: [lang] Proposal (2): isEmpty > > > Proposal for methods: > > - isEmpty() - true for "" or null > - isNotEmpty() - opposite > - isEmptyNN() - true for "" > > - isBlank() - trims - true for " ", "" or null > - isNotBlank() - opposite > - isBlankNN() - trims - true for " " or "" > > - isWhitespace() - true for all whitespace, "" or null > - isNotWhitespace() - opposite > - isWhitespaceNN() - true for all whitespace or "" > > Where NN means NotNull. > This covers all the cases, and takes the working premise that > more people want null to be true than false. > > > Proposal for location: > 1) In StringUtils. Incompatable change to isEmpty() (no > longer trims) and > isWhitespace() (null now true). > > 2) In StringTests (new class). Deprecate StringUtils > isEmpty/isNotEmpty. > > > I prefer the incompatable change #1. We are offering a simply > named alternative. Also, some people already don't expect > isEmpty to trim. And Tapestry and Turbine should both be OK. > > Stephen > > PS. If no agreement is forthcoming, then we shall have to > revert to the 1.0 methods in order to get a release. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
