This source element type is used to copy a directory from the source location to the destination location. All included subdirectories will also copied. The optional attribute srcdir ist used for directories that are located in a different place in the source hierarchy and/or have a different name.

This source element type is used for files that are used without modification. The source file is copied from the source location to the destination location. The optional attributes srcdir and srcfile are used for files that are located in a different place in the source hierarchy and/or have a different source file name.

The optional attribute srcurl is used to specify a source directory with an url. This supports basic authentification. If this srcurl property is set srcdir is ignored. The standard transformation supports the protocls http and https.

The value of attribute type should be def or impl when the file contains definitions (e.g. a C/C++ Header) or implementations. For most other files the type misc is appropriate.

This source element type is used to append text or another file to a file. The content is taken either from a file if srcdir and srcfile are given, or from a string if content is given. If taken from a string, attribute encoding can be used to specify the character encoding of the string content. The attribute mode is used to specify the point at which this content is appended to the file, i.e.before or after the child parts of the current node's parent part are visited. The default value isbefore .

This source element type is used to copy an XML document and optionally to save the copy to a file. Special conditional attributes on the nodes of the XML document are dynamically evaluated to decide whether this node (and its subnodes) are copied into the result document. The name of the evaluated condition attribute is specified using the attribute conditionname and defaults to pv:condition . If the attribute copycondition is not set tofalse , the condition attribute is copied into the target document as well. If the attributevaluesubstitution is set to true , the content of all attribute values of the XML document will be handled asSection 9.5.5, “ ps:pvscltext ” .

The condition itself has to be a valid pvSCL expression. For details on writing pvSCL expressions, see Section 9.7, “Expression Language pvSCL” .

In the example document given below after processing with an ps:pvsclxml transformation, the resulting XML document only contains an introductory chapter if the corresponding featureWithIntroduction is selected.

<?xml version='1.0'?>
<text xmlns:pv="http://www.pure-systems.com/purevariants">
  <chapter pv:condition="WithIntroduction">
    This is some introductory text.
  </chapter>
  <chapter>
    This text is always in the resulting xml output.
  </chapter>
</text>

Source document:

<?xml version='1.0'?>
<version xmlns:pv="http://www.pure-systems.com/purevariants">
  <pv:eval>Version->version</pv:eval>
</version>

Result document:

<?xml version='1.0'?>
<version xmlns:pv="http://www.pure-systems.com/purevariants">
  1.0
</version>

This source element type is used to copy a text document and optionally to save the copy to a file. Special statements in the text document are evaluated to decide which parts of the text document are copied into the result document, or to insert additional text. If no text document encoding is given, then UTF-8 encoding is assumed.

The statements (macro-like calls) that can be used in the text document are listed in the following table.

These statements can occur everywhere in the text document and are directly matched, i.e. independently of the surrounding text. The conditions of PVSCL:IFCOND and PVSCL:ELSEIFCOND and the expression ofPVSCL:EVAL are the same as the conditions described for source element typeps:pvsclxml (see Section 9.5.4, “ ps:pvsclxml ” for details), except for a list of comma-separated flags that can follow the pvSCL code. Following flags are supported.

/* PVSCL:IFCOND(Temperature,LINE) */
initializeSensor("temperature",PVSCL:EVAL(Temperature->max));
/* PVSCL:ELSECOND */
disableSensor("temperature");
/* PVSCL:ENDCOND */

initializeSensor("temperature",60);

//PVSCL:IFCOND(WindSpeed,LINE)updateSensor("wind");PVSCL:ENDCOND

updateSensor("wind");

/* PVSCL:IFCOND(Temperature,BLANKS) */
initializeSensor("temperature",PVSCL:EVAL(Temperature->max));
/* PVSCL:ELSECOND */
disableSensor("temperature");
/* PVSCL:ENDCOND */

/*                                  */
initializeSensor("temperature",60);
/*                  
                             
                 */

//PVSCL:IFCOND(WindSpeed,BLANKS)updateSensor("wind");PVSCL:ENDCOND

//                              updateSensor("wind");     

Conditional text blocks can be nested. That means, that a PVSCL:IFCOND block can contain another PVSCL:IFCOND block defining a nested conditional text block that is evaluated only if the surrounding text block is included in the resulting text output.

In the example document given below after processing with an ps:pvscltext transformation, the resulting text document only contains an introductory chapter if the corresponding featureWithIntroduction is selected.

PVSCL:IFCOND(WithIntroduction)
    This text is in the resulting text output 
    if feature WithIntroduction is selected.
PVSCL:ELSECOND
    This text is in the resulting text output 
    if feature WithIntroduction is not selected.  
PVSCL:ENDCOND
    This text is always in the resulting text output.

This source element type is used to generate C/C++-Header files containing #define <flag> <flagValue> statements. The <flagValue> part of these statements is the value of the attributeValue of the parent part element. The name of the flag is specified by the attributeflag . See the section called “Providing Values for Part Elements” for more details. The same file location can be used in more than oneps:flagfile definition to include multiple #define statements in a single file.

#ifndef __guard_DEBUG
#define __guard_DEBUG 
#undef DEBUG 
#define DEBUG 1 
#endif

This source element type is used to generate makefile variables using a<variable> += '<varValue>' statement. The <varValue> part of the statement is the value of the attributeValue of the parent part element. The name of the variable is specified by the attributevariable . See the section called “Providing Values for Part Elements” for more details. The attribute set defines if the variable is set to the value (true) or if the variable is extended by the value (false). The generated code is compatible with the gmake system. To generate code for a different make system the attributemakesystem can be used. The same file location can be used for more than oneps:makefile element to include multiple makefile variables in a single file.

CXX_OPTFLAGS += "-O6"

This source element type is used to support different classes with different names that are concurrently used in the same place in the class hierarchy. This transformation is C/C++ specific and can be used as an efficient replacement for templates in some cases. This definition is only used in conjunction with the part type ps:classalias . A typedef className alias; statement is generated by the standard transformation for this element type.className is the name of the class referenced by the parent ps:classalias part element. Furthermore, in the standard transformation #include directives are generated for each of the referenced class' ps:file source elements that have a type attribute with the value 'def'. The optional attribute includebasedir defines how the #include directives referencing the class header files will be generated. If this attribute is missing or it has an empty value, the generated #include directives will reference the class header file by absolute file paths. Otherwise the value will be used as the base directory path. In that case the generated #include directives will reference the class header files by a file paths relative to that base directory. If the alias name contains a namespace prefix, corresponding namespace blocks are generated around the typedef statement.

#ifndef __PCConn_include__ 
#define __PCConn_include__ 
#include "C:/Weather Station Example/output/usr/wm-src/NoConn.h"
namespace io {
namespace net {
typedef NoConn PCConn; 
}
}
#endif __PCConn_include__

#ifndef __PCConn_include__ 
#define __PCConn_include__ 
#include "NoConn.h"
namespace io {
namespace net {
typedef NoConn PCConn; 
}
}
#endif __PCConn_include__

This source element type is used to create a symbolic link to a file or directory named <linktarget> .