Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <1060000239.3f2e51ef84284@mungoknotwise.com>
Date: Mon,  4 Aug 2003 08:30:39 -0400
From: steve@mungoknotwise.com
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [lang] DateUtils parseCVS with time format
References: <001301c35a1c$f76c4d40$6f00a8c0@YellowJacket>
 <007501c35a26$103260e0$ed218051@oemcomputer>
In-Reply-To: <007501c35a26$103260e0$ed218051@oemcomputer>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.1

Quoting Stephen Colebourne <scolebourne@btopenworld.com>:

> The parseCVS h:mm z now fails on my PC.
> 
> Locale en_GB, timezone Europe/London. GMT+01:00

Does the actual method fail, or the test? I tweaked the DateUtils class, but I 
didn't touch that part of the parseCVS method. I did add a test for "h:mm z", 
but it passed on my system (I don't have the locale right in front of me at the 
moment). 

> 
> Stephen
> 
> ----- Original Message -----
> From: "Steven Caswell" <steve@mungoknotwise.com>
> To: "'Jakarta Commons Developers List'" <commons-dev@jakarta.apache.org>
> Sent: Monday, August 04, 2003 1:11 AM
> Subject: RE: [lang] DateUtils parseCVS with time format
> 
> 
> And I should have said that I don't know the CVS behavior either.
> 
> So I guess the next question is how closely should we try to mimic the CVS
> format, given that this is the parseCVS method. Are we trying to approximate
> the behavior, or do we believe someone will need it to behave as it were
> strictly compliant to CVS behavior?
> 
> 
> Steven Caswell
> steve@mungoknotwise.com
> a.k.a Mungo Knotwise of Michel Delving
> "One ring to rule them all, one ring to find them..."
> 
> 
> > -----Original Message-----
> > From: Stephen Colebourne [mailto:scolebourne@btopenworld.com]
> > Sent: Sunday, August 03, 2003 6:58 PM
> > To: Jakarta Commons Developers List
> > Subject: Re: [lang] DateUtils parseCVS with time format
> >
> >
> > I don't know the CVS answer, but todays date makes more sense
> > here. Stephen
> >
> > ----- Original Message -----
> > From: "Serge Knystautas" <sergek@lokitech.com>
> > To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
> > Sent: Monday, August 04, 2003 12:46 AM
> > Subject: Re: [lang] DateUtils parseCVS with time format
> >
> >
> > > Steven Caswell wrote:
> > > > One of the supported formats for input to parseCVS is h:mm z. The
> > > > method parses the time correctly, but the date is left as the
> > > > default of
> > January 1,
> > > > 1970. Does this make sense, or does it make sense to have
> > it fill in
> > > > the current date? Since the API is silent on the expected
> > behavior,
> > > > it is difficult to test the API for correctness.
> > >
> > > Do you know how CVS works?  does it set the date as that
> > time in the
> > > last 24 hours, or does it always set today's date?  There are some
> > > unit tests that are based on the current time, so I can put
> > together
> > > unit tests and correct this behavior once I'm sure what it
> > should be.
> > >
> > > --
> > > Serge Knystautas
> > > President
> > > Lokitech >> software . strategy . design >>
> > http://www.lokitech.com/
> > > p. 1.301.656.5501 e. sergek@lokitech.com
> > >
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
> >
> >
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
>