[Bug java/19677] invalid "may not have been initialized" error

2007-01-09 Thread tromey at gcc dot gnu dot org
--- Comment #5 from tromey at gcc dot gnu dot org 2007-01-09 20:46 --- All gcj front end bugs have been fixed by the gcj-eclipse branch merge. I'm mass-closing the affected PRs. If you believe one of these was closed in error, please reopen it with a note explaining why. Thanks. -- t

[Bug java/19677] invalid "may not have been initialized" error

2005-01-30 Thread tromey at gcc dot gnu dot org
--- Additional Comments From tromey at gcc dot gnu dot org 2005-01-30 19:02 --- Yes, the underlying problem is the same as with bug 16839. gcj captures all 'final' local variables in an anonymous class. This is incorrect -- it should only capture those which are actually used. -- ht

[Bug java/19677] invalid "may not have been initialized" error

2005-01-28 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-28 19:43 --- Related to bug 16839. The problem might be the same problem after all because final are collected for anonymous inner classes. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19677

[Bug java/19677] invalid "may not have been initialized" error

2005-01-28 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-28 19:35 --- Confirmed, reduced to: class a1 { public int f(){return 1;} } class t { Object f; void g(a1 a) {} void f() { final a1 a; a = new a1 () { public int f(){return 0;}}; g(a); } } --