[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [PATCH] Field position attribute handling
From: |
Jeroen Frijters |
Subject: |
RE: [PATCH] Field position attribute handling |
Date: |
Wed, 19 Nov 2003 10:44:33 +0100 |
Dalibor Topic wrote:
> 7 is the largest prime, that's still an iconst, iconst_7, afaik. That
> makes it take less bytecode.
Actually, iconst_5 is the maximum, but this seems like a little too low
level view of the problem space ;-)
> If two objects are not equal, they should have different hashCodes.
No this isn't true, however, if two objects are equal, they must have
identical hashCodes. It would be nice if unequal objects had different
hashCodes, but this is not a requirement.
Regards,
Jeroen
- Re: 2nd attempt at Re: The right way(tm) of writing toString() (Was: Re: [PATCH] Field position attribute handling), (continued)
- Re: [PATCH] Field position attribute handling, Tom Tromey, 2003/11/18
- Re: [PATCH] Field position attribute handling, Dalibor Topic, 2003/11/18
- Re: [PATCH] Field position attribute handling, Dalibor Topic, 2003/11/19
- Re: [PATCH] Field position attribute handling, Tom Tromey, 2003/11/19
- Re: [PATCH] Field position attribute handling, Dalibor Topic, 2003/11/19
- Re: [PATCH] Field position attribute handling, Tom Tromey, 2003/11/19
- Re: [PATCH] Field position attribute handling, Dalibor Topic, 2003/11/19
RE: [PATCH] Field position attribute handling,
Jeroen Frijters <=