Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 99797 invoked from network); 19 Feb 2002 03:02:58 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 19 Feb 2002 03:02:58 -0000 Received: (qmail 6983 invoked by uid 97); 19 Feb 2002 03:03:03 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 6963 invoked by uid 97); 19 Feb 2002 03:03:02 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 6950 invoked from network); 19 Feb 2002 03:03:01 -0000 Message-ID: <018501c1b8f1$ed039a70$6401a8c0@darden.virginia.edu> From: "Erik Hatcher" To: "Ant Developers List" References: <20020219021628.91942.qmail@web13402.mail.yahoo.com> Subject: Re: bug Date: Mon, 18 Feb 2002 22:02:53 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Diane Holt" > --- Erik Hatcher wrote: > > I had touched this module a while back because the default values were > > not working properly so I was afraid I might have broken it. > > Well, we both kind of did :) You did with your big change, and me with my > little one. I'm not sure if my previous patch broke it worse or just left something broken while fixing the default value stuff. > Yep -- did it a little too quick, and didn't see that a value to add or > subtract could even be specified (thought it was always just inc/dec by > 1). > > Basically, the problem was that, if a value was in fact specified and > there was an old value as well, then you've got another number to deal > with that you weren't taking into account (ie., assigning the old value to > an int, so it could be added to value, and actually adding it). IOW: You > can't just say 'newValue += value', because there's no addition to value > of oldValue that way. > > Anyway, I've put through another fix, and hopefully, this one will fix it > for real. Also a little too quick on this patch too.... you're missing that there are two other formats that need to be taken into account (String and Date) that all have similar logic. I'm refactoring now to at least pull the confusing logic out into a single method that all three types use. I'll be superseding your change either tonight or tomorrow. Why no test cases for this? I don't want to be too much of a stickler since it is a lot of work, but adding more and more test cases makes our reliability that much better. We should probably at least write test cases to identify known bugs while we are fixing them, especially for something like which is easily testable. Erik -- To unsubscribe, e-mail: For additional commands, e-mail: