I give up on print in writer.slate

[Lee Salzman]

The problem had nothing to do with the ArrayNode at all. The problem was
that

UnaryMessageNode
  selector: lobby
  arguments: {ImplicitArgumentNode}

was the role in this case. ImplicitArgumentNode did not define a print
method, and so used the default print method. The default print method
was simply buggy and called itself.

Anyway, I checked in fixes for all of this stuff into CVS. LiteralNodes
currently don't print properly because printOn: still needs to be fixed
in the interpreter, but DO NOT worry about this, since Brian is working
on it as we speak.

Lee

On Tue, Jun 03, 2003 at 01:23:23AM +0000, Paul Dufresne wrote:
> I have a problem in writer.slate about print of roles of MethodNode.
> It try to put roles statements inside an ArrayNode statements, then print 
> it.
> Printing ArrayNode is based on the fact that an ArrayNode is a 
> CompoundStatementNode.
> That is, ArrayNode resend, to print it's contents.
> 
> But as soon I try to add roles statements in ArrayNode statements, the 
> ArrayNode stop
> to be a CompoundStatementNode, so that the resend in ArrayNode, call 
> itself, filling
> the stack.
> 
> Normally, ArrayNode statements is {}. Someone able to copy roles in the 
> ArrayNode while
> keeping it a CompoundStatementNode?
>