When I add a read/write context of type Scope to arrow -sc-> that always returns a Constraint, the generated code for R_sc_Constraint gains an @Child field _1 of type I_Scope, which makes sense.
But then in the constructor of that Java class, it calls adoptChild, but R_* classes don’t extend AbstractNode so that leaves me with faulty code. If I try to remove adoptChild the code compiles. But I’m not sure if that’s the correct approach, as the old way of doing this was using an extra constructor ScC to return both a Scope and Constraint (and use a read context Scope), and that constructor extended AbstractNode and had a specializeChildren defined.

Submitted by Jeff Smits on 11 May 2015 at 19:22

Log in to post comments