Yes. So first of all build is red because of mondrian conflicts. Mondrian defines acceptVisitor: aVisitor in Object as "aVisitor visitNode: self". This way if during parsing something wasn't parsed into an AST node with defined acceptVisitor: method, or wasn't initialized properly e.i. something returns nil then we end up in the infinite loop. That's why job is red and not yellow.
Now the thing about the PetitJava. I see the parsed Java AST as wrapped expressions. This way type cast wraps expression that is casts into some type, negation expression wraps an expression that is negates. Chris sees it as properties for example accessor node has a property for cast and a flag for negation. Also in his vision a node should store an array of accessors if they follow each other whereas I say that there should be a couple of nodes wrapping each other. Also I think that code should be refactored as right now accessor node has negation flag with getters and setters, same is defined for method invocation. This functionality should be moved into a common superclass, same should be applied for type cast etc... Also it's a bit frustrating that one node can be created as a result of parsing several different grammar entities (you can read my full impression in previous PetitJava discussion).
It's fine that we have different views on the development as we can develop two different things. But if we want to have one project in Moose platform, other members of community should help to decide what we are developing.
Uko
Надіслано з iPhone
I missed that mail :). I could not keep up with what was happening with PetitJava during my holidays, but I certainly think it is a piece that people care about (at least from a user point of view). Your and Chris's efforts are certainly appreciated.
In any case, I am not sure I understand why you think that PetitJava is really the problem given that the petitjava build is green. Could you elaborate?
Cheers,
Doru