Updated documentation based on new install instruction functionality.

Author: Bob Garner

docs/GettingStarted.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: GettingStarted)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: GettingStarted.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Getting Started

docs/Transforms.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: Transforms)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: Transforms.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Transforms

docs/edl/EDL.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Entity Definition Language

docs/edl/EDL_Configuration.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL_Configuration)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL_Configuration.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Configuration

docs/edl/EDL_Domain.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL_Domain)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL_Domain.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Domain

docs/edl/EDL_Entity.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL_Entity)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL_Entity.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Entity

docs/edl/EDL_Interface.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL_Interface)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL_Interface.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Interfaces

docs/edl/EDL_Space.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL_Space)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EDL_Space.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Space

docs/emc/EMC.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EMC)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: EMC.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Entity Model Classes

docs/etl/ETL.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: ETL)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: ETL.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Entity Transform Language

docs/etl/ETL_Instructions.md

@@ -1,5 +1,5 @@
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
-[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: ETL_Instructions)
+[//]: # (DO NOT EDIT THIS DOCUMENT, IT WAS GENERATED BY FILE: ETL_Instructions.md)
 [//]: # (!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
 
 # Template Instruction Reference
@@ -331,6 +331,7 @@ Instructions that perform some type of file operation.
 
 | Instruction | Summary |
 |-------------|---------|
+| [`assert`](#instruction_assert) | Tests the provided condition expression and if fails will print the provided message. If the *level* is not specified or is `fatal` the compiler will exit. |
 | [`file`](#instruction_file) | Allows you to direct the template output to a file. |
 | [`import`](#instruction_import) | Imports a file into the template engine and executes it. |
 | [`install`](#instruction_install) | Provides an easy way to install files into your local project. |
@@ -340,6 +341,28 @@ Instructions that perform some type of file operation.
 
 <hr/>
 
+<a name="instruction_assert"></a>
+### `assert`
+
+This is similar to a `$[log fatal]` but with some advantages. Firstly, it is more compact since it basically includes a surrounding `if` block. Secondly, you have the ability to assert to a non-fatal level but still have that exit (such as when you are debugging). Thirdly, you can perform multiple asserts at an `error` level followed by a final `fatal` assert that will fire if any error` asserts occurred previously - thus allowing you to find and report possibly multiple issues before exiting.
+
+#### Usage
+
+> `$[assert `*condition* *level*`]` ...***template-block***... `$[/assert]`
+
+#### Arguments
+
+| Argument | Type | Description |
+|----------|------|-------------|
+| *condition* | `FTExpression` | The assert executes when this condition evaluates to **false**. The condition can involve one of the special assert global variables (e.g., `__assert_error`, `__assert_warning`, ...) to gather up many asserts into a fatal assert. For instance, `$[assert !__assert_error fatal]Cannot proceed.$[/assert]` |
+| *level* | `String` | The level can be used to classify the level of severity of the log output. The options are `info`, `debug`, `warning`, `error` and `fatal`. For the first three the only difference in the output is the prefix of each line which is the level name in all caps followed by `> `. For `error`, output is directed to system error. For `fatal`, output is also sent to system error but after the output, the compiler terminates, stopping any further execution of the template. |
+
+#### *template-block*
+
+If the assert condition is **not** met, the contents of this assert block is sent to the log as the level provided.
+
+<hr/>
+
 <a name="instruction_file"></a>
 ### `file`
 
@@ -385,7 +408,7 @@ You can import template files that simply contain function declarations so that
 <a name="instruction_install"></a>
 ### `install`
 
-When setting up a project using files from a library, this instruction makes it easy to install files from that library into the project directory structure. The files being installed have their native file extension (not the one we use for templates) so they are easily viewable and edited (using the code highlighter appropriate for them). You can also include template code in them and the template code will execute during the install process. Of course, the presence of the template code may interfere with the code highlighter and as well, the template code will not be appropriately highlighted but when the amount of template code is relatively small it can be very advantageous to use this install method over just making it a template and running the template.
+When setting up a project using files from a library, this instruction makes it easy to install files from that library into the project directory structure. The files being installed have their native file extension but ultimately end with the .eml extension. You can include template code in them and the template code will execute during the install process. Using this `install` instruction instead of the `import` has the advantage that you do not need to include a `file` instruction to create the output file, the template being installed is the file (after of course being transformed by its template code). 
 
 #### Usage
 

src/ec/doc/markdown/EDL.md renamed to src/ec/doc/markdown/EDL.md.eml

@@ -39,13 +39,11 @@
         summary = "Provides an easy way to install files into your local project.",
         description = "When setting up a project using files from a library, this instruction makes it easy "
                       + "to install files from that library into the project directory structure. The files being installed "
-                      + "have their native file extension (not the one we use for templates) so they are easily "
-                      + "viewable and edited (using the code highlighter appropriate for them). You can also include "
-                      + "template code in them and the template code will execute during the install process. "
-                      + "Of course, the presence of the template code may interfere with the code highlighter and "
-                      + "as well, the template code will not be appropriately highlighted but when the amount of "
-                      + "template code is relatively small it can be very advantageous to use this install method over "
-                      + "just making it a template and running the template.")
+                      + "have their native file extension but ultimately end with the .eml extension. You can include "
+                      + "template code in them and the template code will execute during the install process. Using "
+                      + "this `install` instruction instead of the `import` has the advantage that you do not need to "
+                      + "include a `file` instruction to create the output file, the template being installed is the file "
+                      + "(after of course being transformed by its template code). ")
 public class FTInstall extends FTNode {
 
     private final FTExpression sourceExpression;