Eager vs Lazy resolution of classes

Thu Jul 22 09:38:00 GMT 2004

Bryce McKinlay writes:
 > Chris Gray wrote:
 > >IMO any code that relies on this behaviour is broken. If that means that some 
 > >Eclipse 2.x versions were broken and Eclipse 3 is not, then that shows that 
 > >the Eclipse guys are learning as they go along.
 > > 
 > >
 > I agree. I think we could actually support this stuff with the
 > BC-ABI, but we'd have to jump through some hoops to do it. As
 > Andrew suggests, it is something that could be added later, if it
 > proves neccessary, provided we don't do anything to preclude it.
It would be fairly easy to support lazy resolution by generating
accessor methods for static data members and using these instead of
getting the addresses directly. All you have to do is create a libffi
thunk that, when called, does the resolution.
I know accessor methods have been discussed before and dismissed, but
they are a very neat solution to this particular problem.
Andrew.