On Mon, Sep 10, 2012 at 9:55 PM, Jonathan Tran <[email protected]> wrote: > That's as far as I've gotten. It's very rough and doesn't handle a lot > of parses yet, but honestly, my biggest unknown now is how to present > the information to the user in a way he/she can interact with it.
You could throw out a prompt. Maybe IRB can help you with that. But then again, why not use the debugger? Note that the OP's goal was different: he wanted to present the state after the execution. For that simply dumping state during execution might be sufficient. But what you are trying to to sounds more like debugging (interaction after the program has finished does not make much sense I guess). Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ -- You received this message because you are subscribed to the Google Groups ruby-talk-google group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at https://groups.google.com/d/forum/ruby-talk-google?hl=en
