Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 38201 invoked from network); 4 Mar 2003 22:10:34 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 4 Mar 2003 22:10:34 -0000 Received: (qmail 28828 invoked by uid 97); 4 Mar 2003 22:12:17 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org Received: (qmail 28820 invoked from network); 4 Mar 2003 22:12:16 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 4 Mar 2003 22:12:16 -0000 Received: (qmail 37347 invoked by uid 500); 4 Mar 2003 22:10:22 -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 37314 invoked from network); 4 Mar 2003 22:10:22 -0000 Received: from smtpout.mac.com (17.250.248.85) by daedalus.apache.org with SMTP; 4 Mar 2003 22:10:22 -0000 Received: from asmtp02.mac.com (asmtp02-qfe3 [10.13.10.66]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h24MASbq011631 for ; Tue, 4 Mar 2003 14:10:28 -0800 (PST) Received: from mac.com ([159.134.168.219]) by asmtp02.mac.com (Netscape Messaging Server 4.15) with ESMTP id HB8W9F00.F0Z for ; Tue, 4 Mar 2003 14:10:27 -0800 Date: Tue, 4 Mar 2003 22:12:21 +0000 Subject: Re: [CLI] Version 2.0 - API Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: John Keyes To: "Jakarta Commons Developers List" Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: <5EE50AD2-4E8E-11D7-A2C8-00039379521C@mac.com> X-Mailer: Apple Mail (2.551) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Still, the original poster had a point - isMandatory would typically > return a boolean, whereas setMandatory would be used for setting the > option. In my code, using CLI 1.0, I've been using isRequired(true) to > specify a required option. The true is not necessary, but makes the > point > that I'm setting something, as opposed to getting the value. I think > requiring that usage might make things a bit clearer, perhaps > deprecating > the old methodology. I accept the point that isXXX should return boolean. I will try to think of a better name for the method and also make it take a boolean parameter to emphasize that the method is indeed setting some state. > As for the mandatory vs. required battle, I have no > preference - they both state what they do in clear language. I have modified it to required to try to keep it more consistent with 1.0. As you say its the name is self-explanatory.. Thanks, -John K - - - - - - - - - - - - - - - - - - - - - - - Jakarta Commons CLI http://jakarta.apache.org/commons/cli --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org