Declarative Programming

From APIDesign

Revision as of 08:02, 20 April 2008 (edit) JaroslavTulach (Talk | contribs) ← Previous diff		Revision as of 08:06, 20 April 2008 (edit) (undo) JaroslavTulach (Talk | contribs) Next diff →
Line 1:		Line 1:
		+	'''Done: 17ef6cbd11b0'''
		+
	s/Turning Machine/Turing Machine		s/Turning Machine/Turing Machine

---

Revision as of 08:06, 20 April 2008

Done: 17ef6cbd11b0

s/Turning Machine/Turing Machine

Put in an explicit example of XML declarative (e.g. NB menus), to make clear how the implementation code builds the menus and how the module exposes a very minimal and high-level SPI to client modules

--RichUnger 22:40, 10 April 2008 (UTC)

• Page 207: As advised in part I, "Empiristic" should be "empirical."
• Page 208: Since you discussed in the testing section how tools can help prevent errors, it might be worth mentioning here that the merged contents of the system filesystem can be viewed right from the IDE at development time (Important Files -> XML Layer -> This layer in context). I can say that number of errors related to malformed layer files have decreased significantly on my team since this tool was introduced and that when errors do occur, they're now much more easily found because of this tool.
  • I'd like to discuss even automatic validation a bit more - if you execute ant -f nbbuild/build.xml commit-validation you will get even compile time errors if your layers are not correct - however that is too much for the book. Let's leave it for wiki.

--TomWheeler Sun Apr 13 16:49:16 CDT 2008