dnode specials

Scripts > Class elements and c++ instructions > Interpreted C++ instructions > node / dnode > dnode specials

node and dnode nearly have the  same interface and therefore can be used analogously. In contrast to node, dnode is part of a xerces document. Such documents open a big room for to the manipulation in the produced C++ code and they can easily be written as XML documents. Trees from dnodes as opposed to such from nodes are also shown in the variable-inspector after a transformation is ended.This lies in the fact, that the document is part plugin which  exists outside the parser while nodes exist only locally within the parser. This is also the reason why dnode class elements cannot be initialized before the beginning of parsing. Only then the plugin is passed into the parser so that the dnodes can be produced by the DOMDocument of the plugin. At the generation of C++ code which uses dnodes the xerces library must be linked. In the project options for the code production the CTT_ParseStateDomPlugin has to be set to as a plugin type then. The evaluation by means of function tables in the exported code isn't implemented yet.

The root node of a dnode tree must be produced with the function GetDocumentElement. The document finally can be written with the function WriteDocument

The way how the document is written is set in the project options.

While label and value of a node can consist of arbitrary characters, the set of the characters for the the label a dnode are restricted on letters, numbers and the underline. The label may  not start with a number or the underline. Special characters aren't permitted here. Exactly the characters are permitted, that are also are permitted for the definition of an XML-tag.

dnode's can be moved in a tree and nodes cannot. This difference was already metionned above.

This page belongs to the TextTransformer Documentation