1 Jul 2003 01:37
Re: Cute screenshot of a ECL prompt
Erik Winkels wrote: | | I'm not using the ECL top-level, at least I think so, but I could just | be confusing terminology here. I just get the input from the Quake2 | console which is always a string, do a c_string_to_object() on that | and feed the result to si_safe_eval(). Then I print the result of the | eval back to the console. | Ahh :). This is what I was doing initially, but to get debugging working, I used CLOS streams masquerading as standard input and output to the default top level, so the debugging prompt was accessable. throw/catch was used to break out of the toplevel loop. There were some issues that seemed to leave ECL in invalid states after an error occurred. The debugger was never properly accessible. I was going to try some other things, but got sidetracked with other issues, and eventually UC was put on ice. I think I had been planning to save the traceback and other information, and write a postmortem debugger. | | It's all still very basic and was mainly a quick hack to see how easy | it would be to communicate with ECL. | | So I don't have debugging going either :) (I had Quake2 crashing on me | whenever I entered an invalid Lisp form until Juanjo pointed me to | si_safe_eval() instead of cl_eval() which I was using uptil that | point.) |(Continue reading)
RSS Feed