public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug classpath/25389] File(new URI("file:./")) -> java.lang.NullPointerException
Date: Tue, 13 Dec 2005 22:01:00 -0000 [thread overview]
Message-ID: <20051213220138.23543.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25389-8961@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from mark at gcc dot gnu dot org 2005-12-13 22:01 -------
(In reply to comment #3)
> Exception in thread "main" java.lang.IllegalArgumentException: URI is not
> hierarchical
> at java.io.File.<init>(File.java:344)
> at myfirstprog.main(myfirstprog.java:16)
Interesting. That is a bit lame. But seems legal since the uri scheme isn't
followed by a double slash so it is indeed not hierarchical.
But since we are constructing such URLs/URIs ourselves (for example in the
SystemClassLoader) through new URL("file", "", -1, "./") it seems wise to
handle them explicitly in the File(URI) constructor.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25389
next prev parent reply other threads:[~2005-12-13 22:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 11:20 [Bug java/25389] New: " caolanm at redhat dot com
2005-12-13 11:46 ` [Bug java/25389] " mark at gcc dot gnu dot org
2005-12-13 13:47 ` [Bug classpath/25389] " mark at gcc dot gnu dot org
2005-12-13 20:07 ` tromey at gcc dot gnu dot org
2005-12-13 22:01 ` mark at gcc dot gnu dot org [this message]
2005-12-14 0:51 ` tromey at gcc dot gnu dot org
2005-12-14 0:51 ` tromey at gcc dot gnu dot org
2005-12-14 8:35 ` caolanm at redhat dot com
2005-12-14 18:35 ` tromey at gcc dot gnu dot org
2005-12-14 18:37 ` tromey at gcc dot gnu dot org
2005-12-14 18:37 ` tromey at gcc dot gnu dot org
2005-12-14 21:28 ` cvs-commit at developer dot classpath 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=20051213220138.23543.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).