RubyGems - gtksourceview3 - Versions diffs - 2.2.4-x64-mingw32 - Mend

gtksourceview3 2.2.4-x64-mingw32

Files changed (334) hide show

data/vendor/local/share/gtk-doc/html/gtksourceview-3.0/lang-tutorial.html ADDED Viewed

@@ -0,0 +1,654 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>GtkSourceView 3 Reference Manual: Language Definition v2.0 Tutorial</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<link rel="home" href="index.html" title="GtkSourceView 3 Reference Manual">
+<link rel="up" href="ch02.html" title="Syntax highlighting reference">
+<link rel="prev" href="ch02.html" title="Syntax highlighting reference">
+<link rel="next" href="lang-reference.html" title="Language Definition v2.0 Reference">
+<meta name="generator" content="GTK-Doc V1.21.1 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle">
+<td width="100%" align="left" class="shortcuts"></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
+<td><a accesskey="u" href="ch02.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
+<td><a accesskey="p" href="ch02.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
+<td><a accesskey="n" href="lang-reference.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="refentry">
+<a name="lang-tutorial"></a><div class="titlepage"></div>
+<div class="refnamediv"><table width="100%"><tr>
+<td valign="top">
+<h2><span class="refentrytitle">Language Definition v2.0 Tutorial</span></h2>
+<p>Language Definition v2.0 Tutorial —
+Guide to the GtkSourceView language definition file format
+</p>
+</td>
+<td class="gallery_image" valign="top" align="right"></td>
+</tr></table></div>
+<div class="refsect1">
+<a name="tutorial"></a><h2>A language definition for the C language</h2>
+<div class="note"><p>
+    The version 2 here refers to the language definition file format,
+    not to the version of GtkSourceView. So this tutorial is suitable
+    for GtkSourceView 2 and 3.
+  </p></div>
+<p>
+To describe the syntax of a language GtkSourceView uses an XML format which
+defines nested context to be highlighted. Each context roughly corresponds
+to a portion of the syntax which has to be highlighted (e.g. keywords,
+strings, comments), and can contain nested contexts (e.g. escaped
+characters.)
+</p>
+<p>
+In this tutorial we will analyze a simple example to highlight a subset of
+C, based on the full C language definition.
+</p>
+<p>
+Like every well formed XML document, the language description starts with a
+XML declaration:
+</p>
+<pre class="programlisting">
+&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+</pre>
+<p>
+After the usual preamble, the main tag is the <code class="code">&lt;language&gt;</code> element:
+</p>
+<pre class="programlisting">
+&lt;language id="c" _name="C" version="2.0" _section="Source"&gt;
+</pre>
+<p>
+The attribute <code class="code">id</code> is used in external references and defines a standard
+way to refer to this language definition, while the <code class="code">name</code> attribute is
+the name presented to the user (it is translatable using gettext prepending a
+<code class="code">_</code>.)
+</p>
+<p>
+The attribute <code class="code">section</code>, also translatable, tells the category where
+this language should be grouped when it is presented to the user. Currently
+available categories in GtkSourceView are "Source", "Script", "Markup",
+"Scientific" and "Other".
+</p>
+<p>
+The attribute <code class="code">version</code> specifies the version of the xml syntax
+used in your language definition file, so it should always be <code class="code">2.0</code>.
+</p>
+<p>
+The <code class="code">&lt;language&gt;</code> element contains three sections:
+<code class="code">&lt;metadata&gt;</code>, <code class="code">&lt;styles&gt;</code> and
+<code class="code">&lt;definitions&gt;</code>
+</p>
+<pre class="programlisting">
+&lt;metadata&gt;
+</pre>
+<p>
+The <code class="code">&lt;metadata&gt;</code> element is optional and provides a collection
+of properties which specify arbitrary information about the language definition
+file itself. It is particularly important to specify the conventional
+<code class="code">mimetypes</code> and <code class="code">globs</code> properties that
+GtkSourceView uses to automatically detect which syntax highlighting to use
+for a given file. They respectively contain a semi-colon separated list of
+mimetypes and filename extensions.
+</p>
+<pre class="programlisting">
+&lt;metadata&gt;
+  &lt;property name="mimetypes"&gt;text/x-c;text/x-csrc&lt;/property&gt;
+  &lt;property name="globs"&gt;*.c&lt;/property&gt;
+&lt;/metadata&gt;
+</pre>
+<pre class="programlisting">
+&lt;styles&gt;
+</pre>
+<p>
+This element contains every association between the styles used in the
+description and the defaults stored internally in GtkSourceView.
+For each style there is a <code class="code">&lt;style&gt;</code> element:
+</p>
+<pre class="programlisting">
+&lt;style id="comment" _name="Comment" map-to="def:comment"/&gt;
+</pre>
+<p>
+This defines a <code class="code">comment</code> style, which inherits the font
+properties from the defaults style <code class="code">def:comment</code>.
+The <code class="code">name</code> attribute contains the translatable name for this
+style, which is the name to show to the user.
+</p>
+<p>
+For each style used in the language definition there is a corresponding
+<code class="code">&lt;style&gt;</code> element; every style can be used in different
+contexts, so they will share the same appearance.
+</p>
+<pre class="programlisting">
+&lt;style id="string" _name="String" map-to="def:string"/&gt;
+&lt;style id="escaped-character" _name="Escaped Character" map-to="def:special-char"/&gt;
+&lt;style id="preprocessor" _name="Preprocessor" map-to="def:preprocessor"/&gt;
+&lt;style id="included-file" _name="Included File" map-to="def:string"/&gt;
+&lt;style id="char" _name="Character" map-to="def:character"/&gt;
+&lt;style id="keyword" _name="Keyword" map-to="def:keyword"/&gt;
+&lt;style id="type" _name="Data Type" map-to="def:type"/&gt;
+</pre>
+<p>
+Following the <code class="code">&lt;styles&gt;</code> element there is the
+<code class="code">&lt;definitions&gt;</code> element, which contains the
+description proper of the syntax:
+</p>
+<pre class="programlisting">
+&lt;definitions&gt;
+</pre>
+<p>
+Here we should define a main context, the one we enter at the beginning of
+the file: to do so we use the <code class="code">&lt;context&gt;</code> tag, with an
+<code class="code">id</code> equal to the <code class="code">id</code> of the
+<code class="code">&lt;language&gt;</code> element:
+</p>
+<pre class="programlisting">
+&lt;context id="c"&gt;
+</pre>
+<p>
+The element <code class="code">&lt;include&gt;</code> contains the list of sub-contexts
+for the current context: as we are in the main context we should put here
+the top level contexts for the C language:
+</p>
+<pre class="programlisting">
+&lt;include&gt;
+</pre>
+<p>
+The first context defined is the one for single-line C style comments: they
+start with a double slash <code class="code">//</code> and end at the end of the line:
+</p>
+<pre class="programlisting">
+&lt;context id="comment" style-ref="comment"&gt;
+  &lt;start&gt;\/\/&lt;/start&gt;
+  &lt;end&gt;$&lt;/end&gt;
+&lt;/context&gt;
+</pre>
+<p>
+The <code class="code">&lt;start&gt;</code> element contains the regular expression telling
+the highlighting engine to enter in the defined context, until the terminating
+regular expression contained in the <code class="code">&lt;end&gt;</code> element is found.
+</p>
+<p>
+Those regular expressions are PCRE regular expressions in the form
+<code class="code">/regex/options</code> (see the documentation of PCRE for details.) If
+there are no options to be specified and you don't need to match the spaces at
+the start and at the end of the regular expression, you can omit the slashes,
+putting here only <code class="code">regex</code>.
+</p>
+<p>
+The possible options are:
+</p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+    <code class="code">i</code>: case insensitive;
+</p></li>
+<li class="listitem"><p>
+    <code class="code">x</code>: extended (spaces are ignored and it is possible to put comments
+    starting with <code class="code">#</code> and ending at the end of the line);
+</p></li>
+<li class="listitem"><p>
+    <code class="code">s</code>: the metacharacter <code class="code">.</code> matches the <code class="code">\n</code>.
+</p></li>
+</ul></div>
+<p>
+You can set the default options using the <code class="code">&lt;default-regex-options</code> tag
+before the <code class="code">&lt;definitions&gt;</code> element. To disable a group of options,
+instead, you have to preced them with a hyphen (<code class="code">-</code>).
+[FIXME: add an example]
+</p>
+<p>
+In GtkSourceView are available also some extensions to the standard perl
+style regular expressions:
+</p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+    <code class="code">\%[</code> and <code class="code">\%]</code> are custom word boundaries, which can
+    be redefined with the <code class="code">&lt;keyword-char-class&gt;</code> tag (in
+    contrast with <code class="code">\b</code>);
+</p></li>
+<li class="listitem"><p>
+    <code class="code">\%{id}</code> will include the regular expression defined in the
+    <code class="code">&lt;define-regex&gt;</code> tag with the same id, useful if you have
+    common portions of regular expressions used in different contexts;
+</p></li>
+<li class="listitem"><p>
+    <code class="code">\%{subpattern@start}</code> can be used only inside the
+    <code class="code">&lt;end&gt;</code> tag and will be substituted with the
+    string matched in the corresponding
+    sub-pattern (can be a number or a name if named sub-patterns are
+    used) in the preceding <code class="code">&lt;start&gt;</code> element. For an example
+    see the implementation of here-documents in the <code class="filename">sh.lang</code>
+    language description distribuited with GtkSourceView.
+</p></li>
+</ul></div>
+<p>
+The next context is for C-style strings. They start and end with a double
+quote but they can contain escaped double quotes, so we sould make sure
+we don't end the string prematurely:
+</p>
+<pre class="programlisting">
+&lt;context id="string" end-at-line-end="true" style-ref="string"&gt;
+</pre>
+<p>
+The <code class="code">end-at-line-end</code> attribute tells the engine that the current context
+should be forced to terminate at the end of the line, even if the ending
+regular expression is not found, and that an error should be displayed.
+</p>
+<pre class="programlisting">
+&lt;start&gt;"&lt;/start&gt;
+&lt;end&gt;"&lt;/end&gt;
+&lt;include&gt;
+</pre>
+<p>
+To implement the escape handling we include a <code class="code">escape</code> context:
+</p>
+<pre class="programlisting">
+  &lt;context id="escape" style-ref="escaped-character"&gt;
+    &lt;match&gt;\\.&lt;/match&gt;
+  &lt;/context&gt;
+</pre>
+<p>
+This is a simple context matching a single regular expression, contained in
+the <code class="code">&lt;match&gt;</code> element. This context will extend its parent, causing the
+ending regular expression of the <code class="code">"string"</code> context to not match the escaped
+double quote.
+</p>
+<pre class="programlisting">
+&lt;/include&gt;
+&lt;/context&gt;
+</pre>
+<p>
+Multiline C-style comment can span over multiple lines and cannot be
+escaped, but to make things more interesting we want to highlight every
+internet address contained:
+</p>
+<pre class="programlisting">
+&lt;context id="comment-multiline" style-ref="comment"&gt;
+  &lt;start&gt;\/\*&lt;/start&gt;
+  &lt;end&gt;\*\/&lt;/end&gt;
+  &lt;include&gt;
+    &lt;context id="net-address" style-ref="net-address" extend-parent="false"&gt;
+</pre>
+<p>
+In this case, the child should be terminated if the end of the parent is
+found, so we use <code class="code">false</code> in the <code class="code">extend-parent</code> attribute.
+</p>
+<pre class="programlisting">
+      &lt;match&gt;http:\/\/[^\s]*&lt;/match&gt;
+    &lt;/context&gt;
+  &lt;/include&gt;
+&lt;/context&gt;
+</pre>
+<p>
+For instance in the following comment the string <code class="code">http://www.gnome.org*/</code>
+matches the <code class="code">net-address</code> context but it contains the end of the parent
+context (<code class="code">*/</code>.) As <code class="code">extend-parent</code> is false,
+only <code class="code">http://www.gnome.org</code> is
+highlighted as an address and <code class="code">*/</code> is correctly recognized as the end of
+the comment.
+</p>
+<pre class="programlisting">
+/* This is a comment http://www.gnome.org */
+</pre>
+<p>
+Character constants in C are delimited by single quotes (<code class="code">'</code>) and can
+contain escaped characters:
+</p>
+<pre class="programlisting">
+&lt;context id="char" end-at-line-end="true" style-ref="string"&gt;
+  &lt;start&gt;'&lt;/start&gt;
+  &lt;end&gt;'&lt;/end&gt;
+  &lt;include&gt;
+    &lt;context ref="escape"/&gt;
+</pre>
+<p>
+The <code class="code">ref</code> attribute is used when we want to reuse a previously defined
+context. Here we reuse the <code class="code">escape</code> context defined in the <code class="code">string</code>
+context, without repeating its definition.
+</p>
+<pre class="programlisting">
+  &lt;/include&gt;
+&lt;/context&gt;
+</pre>
+<p>
+Using <code class="code">ref</code> it is also possible to refer to contexts defined in other
+languages, preceding the id of the context with the id of the containing
+language, separating them with a colon:
+</p>
+<pre class="programlisting">
+&lt;context ref="def:decimal"/&gt;
+&lt;context ref="def:float"/&gt;
+</pre>
+<p>
+The definitions for decimal and float constants are in a external file,
+with id <code class="code">def</code>, which is not associated with any language but contains
+reusable contexts wich every language definition can import.
+</p>
+<p>
+The <code class="code">def</code> language file contains an <code class="code">in-comment</code> context that can contain
+addresses and tags such as FIXME and TODO, so we can write a new version of
+our <code class="code">comment-multiline</code> context that uses the definitions from <code class="code">def.lang</code>.
+</p>
+<pre class="programlisting">
+&lt;context id="comment-multiline" style-ref="comment"&gt;
+  &lt;start&gt;\/\*&lt;/start&gt;
+  &lt;end&gt;\*\/&lt;/end&gt;
+  &lt;include&gt;
+    &lt;context ref="def:in-comment"/&gt;
+</pre>
+<pre class="programlisting">
+  &lt;/include&gt;
+&lt;/context&gt;
+</pre>
+<p>
+Keywords can be grouped in a context using a list of <code class="code">&lt;keyword&gt;</code>
+elements:
+</p>
+<pre class="programlisting">
+&lt;context id="keywords" style-ref="keyword"&gt;
+  &lt;keyword&gt;if&lt;/keyword&gt;
+  &lt;keyword&gt;else&lt;/keyword&gt;
+  &lt;keyword&gt;for&lt;/keyword&gt;
+  &lt;keyword&gt;while&lt;/keyword&gt;
+  &lt;keyword&gt;return&lt;/keyword&gt;
+  &lt;keyword&gt;break&lt;/keyword&gt;
+  &lt;keyword&gt;switch&lt;/keyword&gt;
+  &lt;keyword&gt;case&lt;/keyword&gt;
+  &lt;keyword&gt;default&lt;/keyword&gt;
+  &lt;keyword&gt;do&lt;/keyword&gt;
+  &lt;keyword&gt;continue&lt;/keyword&gt;
+  &lt;keyword&gt;goto&lt;/keyword&gt;
+  &lt;keyword&gt;sizeof&lt;/keyword&gt;
+&lt;/context&gt;
+</pre>
+<p>
+Keywords with different meaning can be grouped in different context, making
+possible to highlight them differently:
+</p>
+<pre class="programlisting">
+&lt;context id="types" style-ref="type"&gt;
+  &lt;keyword&gt;char&lt;/keyword&gt;
+  &lt;keyword&gt;const&lt;/keyword&gt;
+  &lt;keyword&gt;double&lt;/keyword&gt;
+  &lt;keyword&gt;enum&lt;/keyword&gt;
+  &lt;keyword&gt;float&lt;/keyword&gt;
+  &lt;keyword&gt;int&lt;/keyword&gt;
+  &lt;keyword&gt;long&lt;/keyword&gt;
+  &lt;keyword&gt;short&lt;/keyword&gt;
+  &lt;keyword&gt;signed&lt;/keyword&gt;
+  &lt;keyword&gt;static&lt;/keyword&gt;
+  &lt;keyword&gt;struct&lt;/keyword&gt;
+  &lt;keyword&gt;typedef&lt;/keyword&gt;
+  &lt;keyword&gt;union&lt;/keyword&gt;
+  &lt;keyword&gt;unsigned&lt;/keyword&gt;
+  &lt;keyword&gt;void&lt;/keyword&gt;
+&lt;/context&gt;
+</pre>
+<p>
+You can also set a prefix (or a suffix) common to every keyword using the
+<code class="code">&lt;prefix&gt;</code> and <code class="code">&lt;suffix&gt;</code> tags:
+</p>
+<pre class="programlisting">
+&lt;context id="preprocessor" style-ref="preprocessor"&gt;
+  &lt;prefix&gt;^#&lt;/prefix&gt;
+</pre>
+<p>
+If not specified, <code class="code">&lt;prefix&gt;</code> and <code class="code">&lt;suffix&gt;</code>
+are set to, respectively, <code class="code">\%[</code> and
+<code class="code">\%]</code>.
+</p>
+<pre class="programlisting">
+  &lt;keyword&gt;define&lt;/keyword&gt;
+  &lt;keyword&gt;undef&lt;/keyword&gt;
+</pre>
+<p>
+Keep in mind that every keyword is a regular expression:
+</p>
+<pre class="programlisting">
+  &lt;keyword&gt;if(n?def)?&lt;/keyword&gt;
+  &lt;keyword&gt;else&lt;/keyword&gt;
+  &lt;keyword&gt;elif&lt;/keyword&gt;
+  &lt;keyword&gt;endif&lt;/keyword&gt;
+&lt;/context&gt;
+</pre>
+<p>
+In C, there is a common pratice to use <code class="code">#if 0</code> to express multi-line
+nesting comments. To make things easier to the user, we want to highlight
+these pseudo-comments as comments:
+</p>
+<pre class="programlisting">
+&lt;context id="if0-comment" style-ref="comment"&gt;
+  &lt;start&gt;^#if 0\b&lt;/start&gt;
+  &lt;end&gt;^#(endif|else|elif)\b&lt;/end&gt;
+  &lt;include&gt;
+</pre>
+<p>
+As <code class="code">#if 0</code> comments are nesting, we should consider that inside a comment
+we can find other <code class="code">#if</code>s with the corresponding <code class="code">#endif</code>s, avoiding
+the termination of the comment on the wrong <code class="code">#endif</code>. To do so we use a
+nested context, that will extend the parent on every nested
+<code class="code">#if</code>/<code class="code">#endif</code>:
+</p>
+<pre class="programlisting">
+  &lt;context id="if-in-if0"&gt;
+    &lt;start&gt;^#if(n?def)?\b&lt;/start&gt;
+    &lt;end&gt;^#endif\b&lt;/end&gt;
+    &lt;include&gt;
+</pre>
+<p>
+Nested contexts can be recursive:
+</p>
+<pre class="programlisting">
+      &lt;context ref="if-in-if0"/&gt;
+    &lt;/include&gt;
+  &lt;/context&gt;
+  &lt;/include&gt;
+&lt;/context&gt;
+</pre>
+<p>
+Because contexts defined before have higher priority, <code class="code">if0-comment</code> will
+never be matched. To make things work we should move it before the
+<code class="code">preprocessor</code> context, thus giving <code class="code">if0-comment</code> a higher priority.
+</p>
+<p>
+For the <code class="code">#include</code> preprocessor directive it could be useful to highlight
+differently the included file:
+</p>
+<pre class="programlisting">
+&lt;context id="include" style-ref="preprocessor"&gt;
+  &lt;match&gt;^#include (".*"|&amp;lt;.*&amp;gt;)&lt;/match&gt;
+  &lt;include&gt;
+</pre>
+<p>
+To do this we use grouping sub-patterns in the regular expression,
+associating them with a context with the <code class="code">sub-pattern</code> attribute:
+</p>
+<pre class="programlisting">
+    &lt;context id="included-file" sub-pattern="1"
+             style-ref="included-file"/&gt;
+</pre>
+<p>
+In the <code class="code">sub-pattern</code> attribute we could use:
+</p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem"><p>
+    0: the whole regular expression;
+</p></li>
+<li class="listitem"><p>
+    1: the first sub-pattern (a sub-espression enclosed in
+    parenthesis);
+</p></li>
+<li class="listitem"><p>
+    2: the second;
+</p></li>
+<li class="listitem"><p>
+    ...
+</p></li>
+<li class="listitem"><p>
+    <code class="code">name</code>: a named sub-pattern with name <code class="code">name</code> (see the PCRE
+    documentation.)
+</p></li>
+</ul></div>
+<p>
+We could also use a <code class="code">where</code> attribute with value
+<code class="code">start</code> or <code class="code">end</code> to
+specify the regular expression the context is referring, when we have both
+the <code class="code">&lt;start&gt;</code> and <code class="code">&lt;end&gt;</code> element.
+</p>
+<pre class="programlisting">
+  &lt;/include&gt;
+&lt;/context&gt;
+</pre>
+<p>
+Having defined a good subset of the C syntax we close every tag still open:
+</p>
+<pre class="programlisting">
+&lt;/include&gt;
+&lt;/context&gt;
+&lt;/definitions&gt;
+&lt;/language&gt;
+</pre>
+</div>
+<div class="refsect1">
+<a name="id-1.3.2.4"></a><h2>The full language definition</h2>
+<p>
+This is the full language definition for the subset of C taken in consideration
+for this tutorial:
+</p>
+<pre class="programlisting">
+&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;language id="c" _name="C" version="2.0" _section="Source"&gt;
+  &lt;metadata&gt;
+    &lt;property name="mimetypes"&gt;text/x-c;text/x-csrc&lt;/property&gt;
+    &lt;property name="globs"&gt;*.c&lt;/property&gt;
+  &lt;/metadata&gt;
+  &lt;styles&gt;
+    &lt;style id="comment" _name="Comment" map-to="def:comment"/&gt;
+    &lt;style id="string" _name="String" map-to="def:string"/&gt;
+    &lt;style id="escaped-character" _name="Escaped Character" map-to="def:special-char"/&gt;
+    &lt;style id="preprocessor" _name="Preprocessor" map-to="def:preprocessor"/&gt;
+    &lt;style id="included-file" _name="Included File" map-to="def:string"/&gt;
+    &lt;style id="char" _name="Character" map-to="def:character"/&gt;
+    &lt;style id="keyword" _name="Keyword" map-to="def:keyword"/&gt;
+    &lt;style id="type" _name="Data Type" map-to="def:type"/&gt;
+  &lt;/styles&gt;
+  &lt;definitions&gt;
+    &lt;context id="c"&gt;
+      &lt;include&gt;
+        &lt;context id="comment" style-ref="comment"&gt;
+          &lt;start&gt;\/\/&lt;/start&gt;
+          &lt;end&gt;$&lt;/end&gt;
+        &lt;/context&gt;
+        &lt;context id="string" end-at-line-end="true" style-ref="string"&gt;
+          &lt;start&gt;"&lt;/start&gt;
+          &lt;end&gt;"&lt;/end&gt;
+          &lt;include&gt;
+            &lt;context id="escape" style-ref="escaped-character"&gt;
+              &lt;match&gt;\\.&lt;/match&gt;
+            &lt;/context&gt;
+          &lt;/include&gt;
+        &lt;/context&gt;
+        &lt;context id="comment-multiline" style-ref="comment"&gt;
+          &lt;start&gt;\/\*&lt;/start&gt;
+          &lt;end&gt;\*\/&lt;/end&gt;
+          &lt;include&gt;
+            &lt;context ref="def:in-comment"/&gt;
+          &lt;/include&gt;
+        &lt;/context&gt;
+        &lt;context id="char" end-at-line-end="true" style-ref="string"&gt;
+          &lt;start&gt;'&lt;/start&gt;
+          &lt;end&gt;'&lt;/end&gt;
+          &lt;include&gt;
+            &lt;context ref="escape"/&gt;
+          &lt;/include&gt;
+        &lt;/context&gt;
+        &lt;context ref="def:decimal"/&gt;
+        &lt;context ref="def:float"/&gt;
+        &lt;context id="keywords" style-ref="keyword"&gt;
+          &lt;keyword&gt;if&lt;/keyword&gt;
+          &lt;keyword&gt;else&lt;/keyword&gt;
+          &lt;keyword&gt;for&lt;/keyword&gt;
+          &lt;keyword&gt;while&lt;/keyword&gt;
+          &lt;keyword&gt;return&lt;/keyword&gt;
+          &lt;keyword&gt;break&lt;/keyword&gt;
+          &lt;keyword&gt;switch&lt;/keyword&gt;
+          &lt;keyword&gt;case&lt;/keyword&gt;
+          &lt;keyword&gt;default&lt;/keyword&gt;
+          &lt;keyword&gt;do&lt;/keyword&gt;
+          &lt;keyword&gt;continue&lt;/keyword&gt;
+          &lt;keyword&gt;goto&lt;/keyword&gt;
+          &lt;keyword&gt;sizeof&lt;/keyword&gt;
+        &lt;/context&gt;
+        &lt;context id="types" style-ref="type"&gt;
+          &lt;keyword&gt;char&lt;/keyword&gt;
+          &lt;keyword&gt;const&lt;/keyword&gt;
+          &lt;keyword&gt;double&lt;/keyword&gt;
+          &lt;keyword&gt;enum&lt;/keyword&gt;
+          &lt;keyword&gt;float&lt;/keyword&gt;
+          &lt;keyword&gt;int&lt;/keyword&gt;
+          &lt;keyword&gt;long&lt;/keyword&gt;
+          &lt;keyword&gt;short&lt;/keyword&gt;
+          &lt;keyword&gt;signed&lt;/keyword&gt;
+          &lt;keyword&gt;static&lt;/keyword&gt;
+          &lt;keyword&gt;struct&lt;/keyword&gt;
+          &lt;keyword&gt;typedef&lt;/keyword&gt;
+          &lt;keyword&gt;union&lt;/keyword&gt;
+          &lt;keyword&gt;unsigned&lt;/keyword&gt;
+          &lt;keyword&gt;void&lt;/keyword&gt;
+        &lt;/context&gt;
+        &lt;context id="if0-comment" style-ref="comment"&gt;
+          &lt;start&gt;^#if 0\b&lt;/start&gt;
+          &lt;end&gt;^#(endif|else|elif)\b&lt;/end&gt;
+          &lt;include&gt;
+            &lt;context id="if-in-if0"&gt;
+              &lt;start&gt;^#if(n?def)?\b&lt;/start&gt;
+              &lt;end&gt;^#endif\b&lt;/end&gt;
+              &lt;include&gt;
+                &lt;context ref="if-in-if0"/&gt;
+              &lt;/include&gt;
+            &lt;/context&gt;
+          &lt;/include&gt;
+        &lt;/context&gt;
+        &lt;context id="preprocessor" style-ref="preprocessor"&gt;
+          &lt;prefix&gt;^#&lt;/prefix&gt;
+          &lt;keyword&gt;define&lt;/keyword&gt;
+          &lt;keyword&gt;undef&lt;/keyword&gt;
+          &lt;keyword&gt;if(n?def)?&lt;/keyword&gt;
+          &lt;keyword&gt;else&lt;/keyword&gt;
+          &lt;keyword&gt;elif&lt;/keyword&gt;
+          &lt;keyword&gt;endif&lt;/keyword&gt;
+        &lt;/context&gt;
+        &lt;context id="include" style-ref="preprocessor"&gt;
+          &lt;match&gt;^#include (".*"|&amp;lt;.*&amp;gt;)&lt;/match&gt;
+          &lt;include&gt;
+            &lt;context id="included-file"
+                     sub-pattern="1"
+                     style-ref="included-file"/&gt;
+          &lt;/include&gt;
+        &lt;/context&gt;
+      &lt;/include&gt;
+    &lt;/context&gt;
+  &lt;/definitions&gt;
+&lt;/language&gt;
+</pre>
+</div>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.21.1</div>
+</body>
+</html>