395
edits
Howto:Syntax highlighting for Nasal: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Syntax highlighting for Nasal (view source)
Revision as of 01:39, 6 November 2013
, 6 November 2013reasons for using syntaxhighlighting
Philosopher (talk | contribs) m (→Syntax highlighting test: yep, I forgot and/or as operators... twice) |
Philosopher (talk | contribs) m (reasons for using syntaxhighlighting) |
||
| Line 1: | Line 1: | ||
There's '''[[Nasal]] syntax-highlighting''' support available for some editors, which is a big advantage, as it makes Nasal coding much easier. It can often point to syntax errors and so reduce the number of tedious time-consuming and unproductive [[FlightGear]] runs. | There's '''[[Nasal]] syntax-highlighting''' support available for some editors, which is a big advantage, as it makes Nasal coding much easier. It can often point to syntax errors and so reduce the number of tedious time-consuming and unproductive [[FlightGear]] runs, and it can be a sort of "guide" to the language, highlighting functions or keywords that are builtin, so you can quickly check if it is "type" or "typeof" by typing each. It also makes understanding other people's code easier, since you have all of the parts visually separated out, like loops, strings, constants, and builtin functions. | ||
== Notepad++ == | == Notepad++ == | ||
| Line 32: | Line 32: | ||
== Vim == | == Vim == | ||
One such editor is the free vim or its gui variant gvim. | |||
It's not for everyone but it's free, and testing it doesn't hurt: http://www.vim.org/. | It's not for everyone but it's free, and testing it doesn't hurt: http://www.vim.org/. | ||