Hi,
* Dmitry (who raised the issue) believes that we should change the
Harmony code to throw the type named in the Javadoc/specification (i.e.
the supertype j.l.IndexOutOfBoundsException).
Dmitry is wrong.
* Nathan believes that the code already abides by the specification and
that there
I agree with George and Mikhail that we should throw the same exception with RI.
Do not forget about developers who expects this behaviour. If their
application works OK on RI and fails with
StringIndexOutOfBoundsException on Harmony they will probably return
to RI. Everybody is lazy and do not
George Harley wrote:
Hi,
I would like to start a little discussion around JIRA issue 436 [1]
which deals with exception throwing compatibility between Harmony and
the RI. I feel it is important to reach a concrete agreement on this
as so far all of the participants in the issue seem to
Is there any way we can couple the mailing list postings to JIRA?
I often find it hard to go back and find the -dev list discussions we
have had for particular issues. If we could have links from JIRA to a
mail archive of subject headers containing HARMONY-XYZ tags that would
be great.
Regards
But the question remains in my mind whether there is any generic type
definition you could write that would allow you to cast the entrySet()
to a SetMap.Entrycapture-of ? extends K, capture-of ? extends V
equivalent?
To put it another way, I would expect that
for (Map.Entry? extends K, ?
Often new threads are created to continue the initial discussion.
Therefore some of e-mails can be marked with different subject and remain
unnoticed.
In my opinion it'd be not bad to use the [h-] tag instead [jira] to
start the discussion.
In this case all related with the Harmony- can
2006/5/11, George Harley [EMAIL PROTECTED]:
Mikhail Loenko wrote:
OK I see.
I had some thoughts on merging the tests. Are we going to merge
several tests
into a single file (thus losing their histories) or we will add a
digit to the names and
put into the same folder?
For example we
+1
George
Geir Magnusson Jr wrote:
I have received the ACQs and the BCC for Harmony-211 in paper form and
have reviewed them, so I can assert that the critical provenance
paperwork is in order. It is not in SVN yet, but I wanted to get this
vote going at the same time as the Intel
+1
George
Geir Magnusson Jr wrote:
I have received the ACQs and the BCC for Harmony-256, so I can assert
that the critical provenance paperwork is in order and in SVN.
Please vote to accept or reject this codebase into the Apache Harmony
class library :
[ ] + 1 Accept
[ ] -1 Reject
+1
George
Geir Magnusson Jr wrote:
I have received the ACQs and the BCC for Harmony-337, so I can assert
that the critical provenance paperwork is in order and in SVN.
This is the contribution from Intel.
Please vote to accept or reject this codebase into the Apache Harmony
class
Hi Gregory,
1. Many shared libraries in classlib are built without -fPIC option. As far as
Thanks for noting this! Looks like fPIC is just missed in several places.
I can create a JIRA issue with the patch because I think that all classlib
shared libraries should be built with -fPIC. Maybe
seems reasonable. I read the whole thread up to this point in time, and
also wonder why combine into big files...?
geir
George Harley wrote:
Hi,
Just a heads up to you all (and especially anyone working in beans just
now) that I would like to make some changes to src/tests in the beans
Gregory Shimansky wrote:
Hello
I know that x86_64 is not supported at the moment (although VM does support
this mode in interpreter only way if ran with -Dvm.use_interpreter=true), so
I tried to do some porting at home where I run gentoo linux [1]. I didn't
succeed in running anything but
George Harley wrote:
* Little old me thinks that there *is* a problem here but that the
solution is to do as the RI does and throw exceptions with the very same
runtime type as the RI. That's based on my interpretation of the
exception-throwing compatibility guidelines [2], in particular
Hi, George
I agree with your point.
Harmony should throw the same type exception as RI unless we have
sufficient reason such as RI conflict with spec,
or RI's behaviour is illogical or Harmony can't produce the same exception
as RI.
On 5/11/06, George Harley [EMAIL PROTECTED] wrote:
Hi,
I
What is the reason for prohibiting throwing a sub-class?
Every existing try... catch construction will work
Do we really want to convert all tests like
try {
do something
fail();
} catch (SomeException e) {
//expected
}
to something like
try {
do something
fail();
} catch
Hi Gregory/Andrey,
On 5/11/06, Andrey Chernyshev [EMAIL PROTECTED] wrote:
I can create a JIRA issue with the patch because I think that all
classlib
shared libraries should be built with -fPIC. Maybe there are other
places
Yes, there are some other places which would have to be slightly
I agree that the easiest way for us is to throw RI or subclass.
Is it 'bad' practice to fix this bug (replace subclass with RI) on user
request and do not think about this problem today?
On 5/11/06, Richard Liang [EMAIL PROTECTED] wrote:
George Harley wrote:
Hi,
I would like to start a
On Thursday 11 May 2006 17:31 Andrey Chernyshev wrote:
I can create a JIRA issue with the patch because I think that all
classlib shared libraries should be built with -fPIC. Maybe there are
other places
Yes, there are some other places which would have to be slightly
corrected to make
On 11 May 2006 at 13:23, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
I *do* sympathize with [psychos like] Mark who has 4 builds at once
Hey! I resent that . . . I said I had at least half a dozen. ;-)
-Mark.
-
Terms of
On Thursday 11 May 2006 20:44 Rana Dasgupta wrote:
Yes, there are some other places which would have to be slightly
corrected to make this buildable on x86_64.
But, may be it makes sense to ensure that everybody can build run it
successfully on the supported (e.g. IA32) configuration
+1
Geir Magnusson Jr wrote:
I have received the ACQs and the BCC for Harmony-256, so I can assert
that the critical provenance paperwork is in order and in SVN.
Please vote to accept or reject this codebase into the Apache Harmony
class library :
[ ] + 1 Accept
[ ] -1 Reject (provide
+1
Geir Magnusson Jr wrote:
I have received the ACQs and the BCC for Harmony-211 in paper form and
have reviewed them, so I can assert that the critical provenance
paperwork is in order. It is not in SVN yet, but I wanted to get this
vote going at the same time as the Intel contribution in
+1
Geir Magnusson Jr wrote:
I have received the ACQs and the BCC for Harmony-199 in paper form and
have reviewed them, so I can assert that the critical provenance
paperwork is in order. It is not in SVN yet, but I wanted to get this
vote going at the same time as the other contributions
Leo Simons skrev den 11-05-2006 14:48:
On Thu, May 11, 2006 at 09:57:04AM +0100, Tim Ellison wrote:
Is there any way we can couple the mailing list postings to JIRA?
Interesting question! I'm sure it should be possible :-)
I played with JIRA the other day. There is
I didn't read through the details, but it does look like what I was
thinking.
Regards,
Tim
Craig Blake wrote:
Out of the box Jira has the ability to monitor a mailing list and attach
messages containing an issue number as comments to that issue. That
might do what you want.
+1
Tim Ellison wrote:
+1
Geir Magnusson Jr wrote:
I have received the ACQs and the BCC for Harmony-256, so I can assert
that the critical provenance paperwork is in order and in SVN.
Please vote to accept or reject this codebase into the Apache Harmony
class library :
[ ] + 1 Accept
[
+1
Tim Ellison wrote:
+1
Geir Magnusson Jr wrote:
I have received the ACQs and the BCC for Harmony-199 in paper form and
have reviewed them, so I can assert that the critical provenance
paperwork is in order. It is not in SVN yet, but I wanted to get this
vote going at the same time as
+1
Tim Ellison wrote:
+1
Geir Magnusson Jr wrote:
I have received the ACQs and the BCC for Harmony-337, so I can assert
that the critical provenance paperwork is in order and in SVN.
This is the contribution from Intel.
Please vote to accept or reject this codebase into the Apache
+1
Tim Ellison wrote:
+1
Geir Magnusson Jr wrote:
I have received the ACQs and the BCC for Harmony-211 in paper form and
have reviewed them, so I can assert that the critical provenance
paperwork is in order. It is not in SVN yet, but I wanted to get this
vote going at the same time as
Gregory,
Interesting investigations. Looks like classlib porting to 64 bit is needed.
Btw, here is another vector for hacking :)
Since the JIT is not ported to em64t yet, but works on ia32, it could
be possible to build 32-bit version of DRLVM using compatibility layer
in linux-x86_64 (gcc
This is cool to watch :)
Gregory Shimansky wrote:
On Thursday 11 May 2006 17:31 Andrey Chernyshev wrote:
I can create a JIRA issue with the patch because I think that all
classlib shared libraries should be built with -fPIC. Maybe there are
other places
Yes, there are some other places which
Mikhail Fursov wrote:
I agree that the easiest way for us is to throw RI or subclass.
+1.
Is it 'bad' practice to fix this bug (replace subclass with RI) on user
request and do not think about this problem today?
In this case, though replace StringIndexOutOfBoundsException with
Hey Guys,
Geir has already been given the heads up on this, but I didn't have
access to post here earlier, so I'm a little behind.
If you didn't catch it, Philippe Mulet announced that the ECJ.jar is now
being built in automated fashion as a separate download:
On 5/11/06, Mikhail Loenko wrote:
2006/5/11, George Harley :
Mikhail Loenko wrote:
OK I see.
I had some thoughts on merging the tests. Are we going to merge
several tests
into a single file (thus losing their histories) or we will add a
digit to the names and
put into the same
On 5/12/06, Jimmy, Jing Lv wrote:
Mikhail Fursov wrote:
I agree that the easiest way for us is to throw RI or subclass.
+1.
Is it 'bad' practice to fix this bug (replace subclass with RI) on
user
request and do not think about this problem today?
In this case, though replace
Note, the RI is NOT throwing ArrayIndexOutOfBoundsExceptions, it is just
letting them happen via invalid array look ups, but in these cases, the
specification is marked with an IndexOutOfBoundsException.
For most methods in StringBuilder and StringBuffer, the specification
specifically states
37 matches
Mail list logo
