At the moment, when I write Nasal scripts, my debugging goes like:
- Change something in the script.
- Write some debugging output into the script, using "print()".
- Startup FlightGear (of course my script resides inside the "data/Nasal" directory).
- Watch the console during FG startup to see what my script's output is.
So, because of step (3), this is pretty time-consuming, since _all_ scripts get loaded and run during FG startup and, of course, because the whole program starts. Seems to me that this is a bit too much effort when you only want to debug one script.
Is there a better way that I do not see? I thought about getting the Nasal compiler from plausible.org, but then I thought that it probarbly will not know all the FG-specific Nasal stuff, right? So, what is your Nasal debugging strategy?
harms
PS: I know of a .vim-File for Nasal syntax highlighting for the Vim-editor. Has anyone heard of something similar for Notepad++?