On Jan 9, 2008 2:45 PM, Justin Heyes-Jones <[EMAIL PROTECTED]> wrote: > On 09/01/2008, Elliott Slaughter <[EMAIL PROTECTED]> wrote: > > On Jan 5, 2008 9:26 AM, Gustavo <[EMAIL PROTECTED]> wrote: > > Is that much code necessary to evaluate an expression?
Probably not, but this was my first attempt so that is how much code it took me to get it working at all. > It would be fairly simple to have a command line on screen that you > can bring up with a key. I might look at coding that up. I would be interested in seeing anything you come up with. > Then your main loop would look like > > loop > on events > prompt key pressed > toggle on screen prompt > prompt submitted (user pressed enter key) > call read and eval on input It isn't necessarily that easy. The user could type something over multiple lines, or multiple inputs over one line. (My code may be long partly to address those cases.) Also, if the user enters input that causes an error, the user shouldn't necessarily get to the debugger. (At least, in CLISP you can't seem to get back to the main loop if you enter the debugger.) (So while coding the above may not be difficult it may not exactly be short code. It may even be just as long as my code.) > update > draw -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert _______________________________________________ application-builder mailing list application-builder@lispniks.com http://www.lispniks.com/mailman/listinfo/application-builder
