From: Andrew John Hughes <gnu_andrew@member.fsf.org>
To: Mark Wielaard <mark@klomp.org>
Cc: tromey@redhat.com, Mauve News Group <mauve-discuss@sources.redhat.com>
Subject: Re: new module
Date: Wed, 21 Jun 2006 18:50:00 -0000 [thread overview]
Message-ID: <1150915803.7451.164.camel@localhost.localdomain> (raw)
In-Reply-To: <1150887245.2600.26.camel@elsschot.wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 2525 bytes --]
On Wed, 2006-06-21 at 12:54 +0200, Mark Wielaard wrote:
> On Wed, 2006-06-21 at 09:45 +0100, Andrew John Hughes wrote:
> > Hallelujah! We might finally see the result of Tom's concurrency patch.
>
> :) We might, but apart from one small typo in the Ecj build script,
> fixed as follows:
>
> 2006-06-21 Mark Wielaard <mark@klomp.org>
>
> * Ecj: Fix jikese typo.
>
> there is a compilation error on the generics branch which might or might
> not be valid (I don't have the language spec handy):
>
> 3. ERROR in ../../classpath/java/util/Collections.java
> (at line 6622)
> (Class<Map.Entry<K,V>>) Map.Entry.class;
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cannot cast from Class<Map.Entry> to Class<Map.Entry<K,V>>
>
> Cheers,
>
> Mark
>
> --- scripts/Ecj 19 Jun 2006 19:53:33 -0000 1.2
> +++ scripts/Ecj 21 Jun 2006 10:48:57 -0000
> @@ -88,7 +88,7 @@
> cd org.eclipse.jdt.core
> exec > ../ecj-native-build/Log.Std 2>&1
> set -e
> -find compiler batch -name \*.java | CLASSPATH=compiler:batch xargs ../ecj-gcj-build/ecj -1.4 -bootclasspath $TOP/classpath/jikese-install/share/classpath/glibj.zip -classpath compiler:batch -d ../ecj-native-build -nowarn
> +find compiler batch -name \*.java | CLASSPATH=compiler:batch xargs ../ecj-gcj-build/ecj -1.4 -bootclasspath $TOP/classpath/jikes-install/share/classpath/glibj.zip -classpath compiler:batch -d ../ecj-native-build -nowarn
> )
>
> Report "ecj built with native-ecj" $? ecj-native-build/Log.Std
>
>
My reading of the language spec. is that ecj is right (and
should have been earlier), but feel free to disagree.
A cast from one parameteric type to another, where both are fully
specified (i.e. no wildcards), is basically an equality test i.e. the
conversion from G(T_1, T_2 ... T_n) to G(S_1, S_2 ... S_n) holds if
S_1 = T_1 etc. where none of T_1..T_n or S_1..S_n are wildcards.
--
Andrew :-)
Please avoid sending me Microsoft Office (e.g. Word, PowerPoint)
attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
If you use Microsoft Office, support movement towards the end of vendor
lock-in:
http://opendocumentfellowship.org/petition/
"Value your freedom, or you will lose it, teaches history.
`Don't bother us with politics' respond those who don't want to learn."
-- Richard Stallman
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html
public class gcj extends Freedom implements Java { ... }
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-06-21 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 16:03 Tom Tromey
2006-06-19 17:03 ` Andrew John Hughes
2006-06-21 7:52 ` Mark Wielaard
2006-06-21 8:45 ` Andrew John Hughes
2006-06-21 10:54 ` Mark Wielaard
2006-06-21 11:36 ` Jeroen Frijters
2006-06-21 18:50 ` Andrew John Hughes [this message]
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=1150915803.7451.164.camel@localhost.localdomain \
--to=gnu_andrew@member.fsf.org \
--cc=mark@klomp.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=tromey@redhat.com \
/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).