On 01/04/2012 17:07, Marvin Humphrey wrote:
On 30/03/2012 23:31, Marvin Humphrey wrote:

This loop construct would make more sense.

   FOR class IN classes
     FOR method IN class.methods
       IF class.method_needs_binding(method)
         generate_binding(method)

A patch implementing this loop logic is below my sig.  However, it causes an
interesting set of test failures.  Here's one of the failing tests:

[...]

This problem is not unique to ANDCompiler, but happens for any class which has
not had bindings specifically requested.

I suspect that the remedy is to automatically generate bindings for *all*
classes and methods in the hierarchy.

Yes, this seems like the right approach to me.

Nick

Reply via email to