Nasal for C++ programmers: Difference between revisions

Jump to navigation Jump to search
m
just to make Philosopher's point :-)
mNo edit summary
m (just to make Philosopher's point :-))
Line 47: Line 47:
use a markup language to describe information and programming languages to
use a markup language to describe information and programming languages to
act on it.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg07574.html|title=<nowiki>Re: [Flightgear-devel] x++ The World's First XML-Based ProgrammingLanguage</nowiki>|author=<nowiki>David Megginson</nowiki>|date=<nowiki>Tue, 09 Jul 2002 11:07:39 -0700</nowiki>}}</ref>|<nowiki>David Megginson</nowiki>}}
act on it.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg07574.html|title=<nowiki>Re: [Flightgear-devel] x++ The World's First XML-Based ProgrammingLanguage</nowiki>|author=<nowiki>David Megginson</nowiki>|date=<nowiki>Tue, 09 Jul 2002 11:07:39 -0700</nowiki>}}</ref>|<nowiki>David Megginson</nowiki>}}
{{cquote|<nowiki>Originally, I defined actions using XML mainly because we didn't have a scripting language, but ideally, we should share up the labour like this:
XML = declarative
NASAL = imperative
i.e. if we want to say "this is X," we use XML; if we want to say "do Y", we use NASAL. A drop-down menu is declarative, but the actions associated with each menu item are imperative, and could be NASAL code snippits. The keymap is declarative, but the actions associated with each keystroke are imperative, and again, could be NASAL code snippits embedded in XML.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18993.html|title=<nowiki>Time to Refactor (was Re: [Flightgear-devel] Re: Nasal integration docs)</nowiki>|author=<nowiki>David Megginson</nowiki>|date=<nowiki>Wed, 26 Nov 2003 15:12:46 -0800</nowiki>}}</ref>|<nowiki>David Megginson</nowiki>}}


<references/>
<references/>

Navigation menu