public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gnu_andrew at member dot fsf dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/11085] SimpleDateFormat fails to parse valid dates
Date: Sat, 22 Jan 2005 03:29:00 -0000	[thread overview]
Message-ID: <20050122032951.20743.qmail@sourceware.org> (raw)
In-Reply-To: <20030604052449.11085.cduffy@spamcop.net>


------- Additional Comments From gnu_andrew at member dot fsf dot org  2005-01-22 03:29 -------
In current Classpath CVS head, parsing of this string is now successful.  The
output of the given test case is:

$ java TestParse
Result: Wed Jun 04 03:09:35  2003
Fail

"Fail" is printed because the value doesn't match the given string.  But, this
string is the time localized to the timezone of where the class is being run. 
Sun outputs this localized String, while, at present, the Classpath one is
always in GMT.  It is clear that the above figure is the time 22:09:35 -0500
shifted five hours forward to GMT.  Sun's VM (1.5) also fails the second bit, as
it produces the localized output "Wed Jun 04 04:09:35 BST 2003" (being run on a
machine in the UK).

Comparing the numeric millisecond values is more accurate, and this shows
equivalent values (1054696175000) for both VMs, and a mental grasp of the
date/time shows that the output is correct.  

The only possible bug remaining here is that the Date.toString() output is
incorrect, as it does not use the timezone field.  Whether this is truly a bug
or not is open to debate, as there appears to be no documentation on this in
java.util.Date other than the requirement for a zzz field.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11085


  parent reply	other threads:[~2005-01-22  3:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030604052449.11085.cduffy@spamcop.net>
2003-06-05 15:09 ` pinskia@physics.uc.edu
2003-06-08  2:04 ` tromey@redhat.com
2003-07-24 15:44 ` pinskia at physics dot uc dot edu
2003-08-23  0:25 ` dhazeghi at yahoo dot com
2005-01-22  3:29 ` gnu_andrew at member dot fsf dot org [this message]
2005-03-23 21:26 ` cvs-commit at gcc dot gnu dot org
2005-03-23 21:36 ` cvs-commit at gcc dot gnu dot org
2005-03-23 21:39 ` tromey at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050122032951.20743.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).