This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/24833] New: Variable declared as 'final' can be assigned in conflict with Java standard
- From: "m4341 at abc dot se" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Nov 2005 11:38:17 -0000
- Subject: [Bug libgcj/24833] New: Variable declared as 'final' can be assigned in conflict with Java standard
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
Example is found in file java.lang.VMCompiler, by code:
private static final MessageDigest md5Digest;
static
{
try
{
md5Digest = MessageDigest.getInstance("MD5");
}
catch (NoSuchAlgorithmException _)
{
md5Digest = null;
}
}
The second assignment in the catch is in conflict with Java standard. (checked
against jdk 1.5.0.)
>From a logical point of view this is not really an error, but from a
conformance point ov view it is.
--
Summary: Variable declared as 'final' can be assigned in conflict
with Java standard
Product: gcc
Version: 4.0.2
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: libgcj
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: m4341 at abc dot se
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24833