r
http://www.eclipse.org/dsdp/tm
> -Original Message-
> From: sebb [mailto:[EMAIL PROTECTED]
> Sent: Samstag, 15. März 2008 02:34
> To: Jakarta Commons Developers List
> Subject: Re: [NET] 1.5 Leap year processing
>
> On 14/03/2008, Oberhuber, Martin
> <[EMAIL PROT
On 14/03/2008, Oberhuber, Martin <[EMAIL PROTECTED]> wrote:
> Hi Sebb,
>
>
> > Regex is not available in Java 1.3.
> > Also, how does one know where the year is in the string?
>
>
> Code for this already is in Commons Net, using ORO for the Regex.
> See UnixFTPEntryParser.java line 105
OK, did
Hi Sebb,
> Regex is not available in Java 1.3.
> Also, how does one know where the year is in the string?
Code for this already is in Commons Net, using ORO for the Regex.
See UnixFTPEntryParser.java line 105
> 2.2 If previous year also gives a parse error then give up?
Hm... Well, well. The po
ind River
> Target Management Project Lead, DSDP PMC Member
> http://www.eclipse.org/dsdp/tm
>
>
>
>
> > -Original Message-
> > From: sebb [mailto:[EMAIL PROTECTED]
> > Sent: Mittwoch, 12. März 2008 21:37
> > To: Commons Developers List
> &
ent Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
> -Original Message-
> From: sebb [mailto:[EMAIL PROTECTED]
> Sent: Mittwoch, 12. März 2008 21:37
> To: Commons Developers List
> Subject: [NET] 1.5 Leap year processing
>
> I think I've found a
I think I've found a solution to the leap year processing.
At present the code tries the short date and then adds the current
year if the parse fails.
This does not work on Java 1.4 or earlier because Feb 29 1970 does not
cause a parse failure - the date is converted to Mar 1 1970.
One solution s
