With inline code members you are able to store within the project some snippets of native code (e.g. C). During code generation these code snippets are output together with other project members strictly according to the order in which the members are defined. Inline code members are represented in Composer by following bricks:

Typical application case is to use inline code to add C #include "..." directives to the generated code. In this manner you can combine the translated Chora platform-independent code with code to communicate with the target system.

Please note, an inline code member can exist only within a unit member. Moreover inline members are considered during code generation only. They have no effect during prototyping.

Adding a new inline code member.

The name of the inline code member has no effect on the function of your application. However, it has to be unique within the unit the inline code member is defined inside.

The content of inline code members is edited in the Code Editor window. For this purpose:

By using the $if, $else, $elseif and $endif Chora conditional compilation directives, parts of the inline code, depending on the target platform, can be excluded. If the condition in an $if or $elseif directive is fulfilled, the following code part is taken over. If the condition is not fulfilled, the code is ignored. For example, the following C compiler #include directive is take over only when generating code for Microsoft Windows target:

You can create any number of copies of an already existing inline code member.

All members are generated strictly according to the order in which they are defined within the unit. The code generation starts always with the back most member (the member with the lowest order number). The actual order of an member can be inspected in the members area of the Inspector window. To change the code generation order you need to explicitly restack the member. For example, to arrange an inline code member at the top of the generated code, do following:

With the attribute Generator you can selectively control, whether the inline code member is taken in account when generating code. Configuring this attribute with the value false will exclude the inline code member from your project.

The following table shows the complete list of attributes provided by the inline code member:

Attribute name	Short description
Brick	Determines the position and the size of a inline code member brick within the Composer window.
Description	Contains the description for the inline code member.
Generator	Controls the code generation for the affected inline code member.

This section describes the Chora syntax of how inline code members are stored inside Embedded Wizard project files. The knowledge about the syntax can be helpful when you plan to process the project contents by third party tools. In particular, the general purpose Export and Import functionality introduced in version 14 requires a good understanding of how project members are represented in Chora syntax to correctly interpret the exported members and synthesize the Chora code for members to import. Please note, Embedded Wizard project files (and thus Chora code) are encoded as text in UTF-8 format.

In Chora syntax, inline code members are always introduced with the keyword inline, followed by the name of the member and a its content (the native code) enclosed between a pair of curly braces {..}. Wherever necessary, the tokens are separated by whitespace signs.

The definition of an inline code member can be initiated by a comment block providing optional description for the member. The content of this comment corresponds to the value of the member's attribute Description. Furthermore the directives $rect and $output can be specified providing values for the corresponding attributes Brick and Generator. The following example demonstrates the described syntax:

Each Chora file (or text exchanged with an external Export and/or Import tool) can be (or even should be) prefixed with $version directive. This directive determines the version number of the included Chora code. For details concerning the syntax of the version please see the chapter $version macro. Furthermore, the code can include a $scope directive followed by a path to a project member acting as the original owner of the corresponding code. That means the members described by the Chora code existed inside the member specified in $scope. In case of an inline code member, $scope would specify the name of the unit the member belongs to.