Reinier Zwitserloot 6c82a3c780 This is a 3-day bughunt that ended up being something extremely simple:
** DO NOT REUSE TYPEREFERENCE OBJECTS **

because that makes the binding process go pearshaped - after hte first run, that TypeReference object's binding parameter is set, and as its set, the resolver won't bother re-resolving it.

However, each parse run starts with new scope objects, and any 2 bindings created by different scopes aren't equal to each other. urrrrrrgh!

Fortunately, a lot of code that 'fixed' methods by adding bindings and scope have all been removed, as the parser patch point is well before these bindings are created. Thus:

** NEVER CREATE YOUR OWN BINDINGS AND SCOPE OBJECTS **

because if it comes down to that, you're doing it entirely wrong. That's eclipse's job. We're patching where we are so you don't have to do this.
2009-06-23 06:01:13 +02:00
2009-06-19 04:48:23 +02:00
2009-06-20 23:29:47 +02:00
S
Description
Very spicy additions to the Java programming language.
BSD-3-Clause, MIT
83 MiB
0 Stars 1 Watchers 0 Forks
Languages
Java 94.6%
HTML 4.8%
JavaScript 0.2%
CSS 0.2%