On Apr 12, 4:40 pm, John J Barton <[email protected]> wrote:
> I guess you looked at getfirebug.com Well, I looked at the wiki, specifically "All pages" and the pages that seemed useful. > I don't break on error. (using 1.6a9) even if I have it set. This completely changes the use case. I'll see if I can install 1.6a9 on any machines. 1.5 is running on installations I can't change. > I guess once I don't understand the first bit the rest does not make > sense. Evidently. The question about aborting from evaluations may apply to other situations though. Good point, that the command line isn't the focus of Firebug's design. > command line API. Then it > calls eval() on the result and sends it back through the Firebug > console object. That's all there is to it. That's all there is to a simple LISP or Scheme too: read a string, evaluate it, and print it. The string may call eval, or call functions that call eval. Many LISPs/Schemes have the idea of abandoning the eval (the outer one, of the string). Many have various forms of stepping or error analysis or error recovery. Features like that aren't completely standardized though. -- Derek -- You received this message because you are subscribed to the Google Groups "Firebug" 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 http://groups.google.com/group/firebug?hl=en.
