<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Syntax :: Ginmake Manual</title>
    <link>https://gems.co.uk/syntax/index.html</link>
    <description>Ginmake parses input source code files and extracts information from comments that are associated with objects in the source code. The syntax of these comments is described in this section.&#xA;Comment Parsing&#xD;Expression Evaluation&#xD;Source Variables&#xD;String Handling / Entity References&#xD;Type Specifiers</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://gems.co.uk/syntax/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Comment Parsing</title>
      <link>https://gems.co.uk/syntax/comment-parsing.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/syntax/comment-parsing.html</guid>
      <description>Definitions can occur in any kind of source code comment, depending upon the source type.&#xA;Note that comments are ignored in sections that have been excluded by conditional compilation (see “The Pre-processor” section).&#xA;For ASM, comments extend from the first ; character seen on a line to the end of the line.&#xA;If the source being compiled is ‘C’ source, then comments can either be traditional multi-line/in-line C style comments /* .. */.</description>
    </item>
    <item>
      <title>Expression Evaluation</title>
      <link>https://gems.co.uk/syntax/expression-evaluation.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/syntax/expression-evaluation.html</guid>
      <description>Expressions can be used in data definitions and in source code (e.g. as an array index). Expressions can be contained within pre-processor symbols. e.g.&#xA;1#define MAP_DIM 10 2#define MAP_SIZE (MAP_DIM * MAP_DIM)Within source code, all expressions are considered to be integer expressions. In numerical fields of data definitions, expressions are either integer or floating-point, depending upon the type of the field. For example, the Scalar field of a parameter is integer unless a ‘*’ character is used to indicate that it is floating-point.</description>
    </item>
    <item>
      <title>Source Variables</title>
      <link>https://gems.co.uk/syntax/source-variables.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/syntax/source-variables.html</guid>
      <description>Variables in the source code can be followed by data definitions comments. Ginmake can be run against C and ASM code.&#xA;Data types recognised by ginmake for C code:&#xA;1uint8 2uint8_t 3int8 4int8_t 5uint16 6uint16_t 7int16 8int16_t 9int24 10int24_t 11int32 12int32_t 13int64 14int64_t 15float 16doubleIf the underlying type is float or double then GWv4 will treat the raw value as floating-point.</description>
    </item>
    <item>
      <title>String Handling / Entity References</title>
      <link>https://gems.co.uk/syntax/string-handling.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/syntax/string-handling.html</guid>
      <description>As of ginmake 1.33, it is possible to use entity references in strings for names etc.&#xA;These are very similar to HTML entity references, but they have a different syntax - the ‘&amp;’ and ‘;’ characters are replaced with the $ symbol.&#xA;e.g.&#xA;&amp;lt; codes for &lt;&#xA;This becomes:&#xA;$lt$ in ginmake syntax.&#xA;Entity references enable us to circumvent the issuse of the DOS and ANSI code pages not entirely overlapping one another and also allows other special characters that may not be present in these codepages.</description>
    </item>
    <item>
      <title>Type Specifiers</title>
      <link>https://gems.co.uk/syntax/type-specifiers.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/syntax/type-specifiers.html</guid>
      <description>Some values may have their type specified.&#xA;This is intended to be used when specifying raw values where there would otherwise be ambiguity over the type that could lead to incorrect values ending up in the output GIN. Additionally for floating-point raw values it is easier to specify them using floating-point values in many cases.&#xA;Format:&#xA;@Nt:VALUE&#xA;Where ‘N’ is the number of bytes in the value (1,2,3,4 or 8).</description>
    </item>
  </channel>
</rss>