Commits

Jason McKesson  committed d3607b6

No more spaces in Doc file names.

  • Participants
  • Parent commits a0c489f

Comments (0)

Files changed (7)

File docs/Command Line Options.xml

-<?xml version="1.0" encoding="UTF-8"?>
-<?oxygen RNGSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng" type="xml"?>
-<?oxygen SCHSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng"?>
-<article xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
-    xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:pg="https://bitbucket.org/alfonse/glloadgen"
-    version="5.0">
-    <title>Command Line Options</title>
-    <para>The command-line options for the code generation tools are explained here. They work more
-        or less like the standard command-line options for typical Linux/Windows programs. Options
-        that have a single value can take their parameters as either
-            <literal>-opt_name=parameter</literal> or <literal>-opt_name parameter</literal>.</para>
-    <para>With Lua on the path, the command-line should be specified as follows:</para>
-    <programlisting>lua pathToLoadgen/LoadGen.lua &lt;output filename> &lt;options></programlisting>
-    <para>The <literal>&lt;output filename></literal> must be specified. The path provided is
-        relative to the current directory. The base filename of the path (everything after the last
-        directory separator) will be decorated as appropriate for generating the output files. You
-        should not provide an extension; the system will provide those as needed. The generated
-        files will append an appropriate prefix, depending on which specifications you are
-        generating (OpenGL, WGL, or GLX), so you can provide the same base filename for all of
-        these.</para>
-    <para>The output filename should be specified before any of the options. You can specify it
-        after the options or even between options, but if you specify it after the
-            <literal>-exts</literal> option (but before any subsequent options), the system will
-        mistake it for an extension name. Just specify it first to be safe.</para>
-    <glosslist>
-        <glossentry>
-            <glossterm>-spec</glossterm>
-            <glossdef>
-                <para>Defines the particular specification to generate loading code for. It must be
-                    one of the following values:</para>
-                <itemizedlist>
-                    <listitem>
-                        <para><literal>gl</literal>: default</para>
-                    </listitem>
-                    <listitem>
-                        <para><literal>glX</literal></para>
-                    </listitem>
-                    <listitem>
-                        <para><literal>wgl</literal></para>
-                    </listitem>
-                </itemizedlist>
-            </glossdef>
-        </glossentry>
-        <glossentry>
-            <glossterm>-prefix</glossterm>
-            <glossdef>
-                <para>The code generation system will try to minimize the number of non-static
-                    global variables it defines as much as possible. However, it will have to use
-                    some non-static variables for various things.</para>
-                <para>Code generated from the different specifications are guaranteed not to have
-                    name collisions. However, if you generate code from the
-                        <emphasis>same</emphasis> specification, with different sets of extensions
-                    or versions, collisions will occur.</para>
-                <para>The prefix option allows you to define a string that will be prepended to any
-                    non-static (or otherwise hidden) global variables, where possible. As such, the
-                    prefix should start with characters that are valid for C/C++ identifiers.</para>
-                <para>If the option is not specified, no prefix will be used.</para>
-            </glossdef>
-        </glossentry>
-        <glossentry>
-            <glossterm>-version</glossterm>
-            <glossdef>
-                <para>The highest version of OpenGL to export. You may <emphasis>only</emphasis> use
-                    this when <literal>-spec</literal> is <literal>gl</literal>. And you must use it
-                    when the specification is <literal>gl</literal>.</para>
-            </glossdef>
-        </glossentry>
-        <glossentry>
-            <glossterm>-profile</glossterm>
-            <glossdef>
-                <para>The OpenGL profile to export. It must be one of the following values:</para>
-                <itemizedlist>
-                    <listitem>
-                        <para><literal>core</literal>: default</para>
-                    </listitem>
-                    <listitem>
-                        <para><literal>compatibility</literal>: It is an error to specify this for
-                            OpenGL versions that do not have the core/compatibility
-                            distinction.</para>
-                    </listitem>
-                </itemizedlist>
-            </glossdef>
-        </glossentry>
-        <glossentry>
-            <glossterm>-style</glossterm>
-            <glossdef>
-                <para>The code generation suite has a number of different ways of outputting the
-                    functions and enumerators that define OpenGL. This option allows the user to
-                    select between these particular mechanisms. It must be one of the following
-                    values:</para>
-                <itemizedlist>
-                    <listitem>
-                        <para><literal>pointer_c</literal>: default.</para>
-                    </listitem>
-                </itemizedlist>
-                <para>The specific meaning of these parameters is explained elsewhere. Note that the
-                    system is designed to be extensible; new styles can be added by modifying an
-                    appropriate script and hooking it into the right place in
-                        <filename>modules/Styles.lua</filename>.</para>
-            </glossdef>
-        </glossentry>
-        <glossentry>
-            <glossterm>-indent</glossterm>
-            <glossdef>
-                <para>The indentation style for the output text. It must be one of the
-                    following:</para>
-                <itemizedlist>
-                    <listitem>
-                        <para><literal>tab</literal>: default</para>
-                    </listitem>
-                    <listitem>
-                        <para><literal>space</literal>: Will use 2 spaces to indent.</para>
-                    </listitem>
-                </itemizedlist>
-            </glossdef>
-        </glossentry>
-        <glossentry>
-            <glossterm>-exts</glossterm>
-            <glossdef>
-                <para>Defines a list of extensions to the given specification to export. Every
-                    argument that doesn't start with a "-" following this option will be assumed to
-                    be an extension name. You do not need to prefix the extensions with GL_, WGL_,
-                    or GLX_, but you may do so if you wish.</para>
-                <para>This argument can be specified multiple times. It is fine to specify an
-                    extension name more than once.</para>
-            </glossdef>
-        </glossentry>
-        <glossentry>
-            <glossterm>-ext</glossterm>
-            <glossdef>
-                <para>Defines a single extension to export. It adds the given parameter to the list
-                    of extensions.</para>
-                <para>This argument can be specified multiple times. It is fine to specify an
-                    extension name more than once.</para>
-            </glossdef>
-        </glossentry>
-        <glossentry>
-            <glossterm>-extfile</glossterm>
-            <glossdef>
-                <para>Specifying dozens of extensions on the command line can be exceedingly
-                    tedious. Therefore, the system can be instructed to read a list of extensions
-                    from a file with this option. The file should be a plain text file, where each
-                    extension is specified on a single line.</para>
-                <para>This argument can be specified multiple times. It is fine to specify an
-                    extension name more than once, either in the file or on the command line.</para>
-                <para>The file's directory is relative to the path where the command line was
-                    invoked.</para>
-            </glossdef>
-        </glossentry>
-        <glossentry>
-            <glossterm>-stdext</glossterm>
-            <glossdef>
-                <para>Works like <literal>extfile</literal>, except that the directory for the file
-                    is relative to the place where the <filename>LoadGen.lua</filename> file
-                    is.</para>
-            </glossdef>
-        </glossentry>
-    </glosslist>
-</article>

File docs/Command_Line_Options.xml

+<?xml version="1.0" encoding="UTF-8"?>
+<?oxygen RNGSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng" type="xml"?>
+<?oxygen SCHSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng"?>
+<article xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
+    xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:pg="https://bitbucket.org/alfonse/glloadgen"
+    version="5.0">
+    <title>Command Line Options</title>
+    <para>The command-line options for the code generation tools are explained here. They work more
+        or less like the standard command-line options for typical Linux/Windows programs. Options
+        that have a single value can take their parameters as either
+            <literal>-opt_name=parameter</literal> or <literal>-opt_name parameter</literal>.</para>
+    <para>With Lua on the path, the command-line should be specified as follows:</para>
+    <programlisting>lua pathToLoadgen/LoadGen.lua &lt;output filename> &lt;options></programlisting>
+    <para>The <literal>&lt;output filename></literal> must be specified. The path provided is
+        relative to the current directory. The base filename of the path (everything after the last
+        directory separator) will be decorated as appropriate for generating the output files. You
+        should not provide an extension; the system will provide those as needed. The generated
+        files will append an appropriate prefix, depending on which specifications you are
+        generating (OpenGL, WGL, or GLX), so you can provide the same base filename for all of
+        these.</para>
+    <para>The output filename should be specified before any of the options. You can specify it
+        after the options or even between options, but if you specify it after the
+            <literal>-exts</literal> option (but before any subsequent options), the system will
+        mistake it for an extension name. Just specify it first to be safe.</para>
+    <glosslist>
+        <glossentry>
+            <glossterm>-spec</glossterm>
+            <glossdef>
+                <para>Defines the particular specification to generate loading code for. It must be
+                    one of the following values:</para>
+                <itemizedlist>
+                    <listitem>
+                        <para><literal>gl</literal>: default</para>
+                    </listitem>
+                    <listitem>
+                        <para><literal>glX</literal></para>
+                    </listitem>
+                    <listitem>
+                        <para><literal>wgl</literal></para>
+                    </listitem>
+                </itemizedlist>
+            </glossdef>
+        </glossentry>
+        <glossentry>
+            <glossterm>-prefix</glossterm>
+            <glossdef>
+                <para>The code generation system will try to minimize the number of non-static
+                    global variables it defines as much as possible. However, it will have to use
+                    some non-static variables for various things.</para>
+                <para>Code generated from the different specifications are guaranteed not to have
+                    name collisions. However, if you generate code from the
+                        <emphasis>same</emphasis> specification, with different sets of extensions
+                    or versions, collisions will occur.</para>
+                <para>The prefix option allows you to define a string that will be prepended to any
+                    non-static (or otherwise hidden) global variables, where possible. As such, the
+                    prefix should start with characters that are valid for C/C++ identifiers.</para>
+                <para>If the option is not specified, no prefix will be used.</para>
+            </glossdef>
+        </glossentry>
+        <glossentry>
+            <glossterm>-version</glossterm>
+            <glossdef>
+                <para>The highest version of OpenGL to export. You may <emphasis>only</emphasis> use
+                    this when <literal>-spec</literal> is <literal>gl</literal>. And you must use it
+                    when the specification is <literal>gl</literal>.</para>
+            </glossdef>
+        </glossentry>
+        <glossentry>
+            <glossterm>-profile</glossterm>
+            <glossdef>
+                <para>The OpenGL profile to export. It must be one of the following values:</para>
+                <itemizedlist>
+                    <listitem>
+                        <para><literal>core</literal>: default</para>
+                    </listitem>
+                    <listitem>
+                        <para><literal>compatibility</literal>: It is an error to specify this for
+                            OpenGL versions that do not have the core/compatibility
+                            distinction.</para>
+                    </listitem>
+                </itemizedlist>
+            </glossdef>
+        </glossentry>
+        <glossentry>
+            <glossterm>-style</glossterm>
+            <glossdef>
+                <para>The code generation suite has a number of different ways of outputting the
+                    functions and enumerators that define OpenGL. This option allows the user to
+                    select between these particular mechanisms. It must be one of the following
+                    values:</para>
+                <itemizedlist>
+                    <listitem>
+                        <para><literal>pointer_c</literal>: default.</para>
+                    </listitem>
+                </itemizedlist>
+                <para>The specific meaning of these parameters is explained elsewhere. Note that the
+                    system is designed to be extensible; new styles can be added by modifying an
+                    appropriate script and hooking it into the right place in
+                        <filename>modules/Styles.lua</filename>.</para>
+            </glossdef>
+        </glossentry>
+        <glossentry>
+            <glossterm>-indent</glossterm>
+            <glossdef>
+                <para>The indentation style for the output text. It must be one of the
+                    following:</para>
+                <itemizedlist>
+                    <listitem>
+                        <para><literal>tab</literal>: default</para>
+                    </listitem>
+                    <listitem>
+                        <para><literal>space</literal>: Will use 2 spaces to indent.</para>
+                    </listitem>
+                </itemizedlist>
+            </glossdef>
+        </glossentry>
+        <glossentry>
+            <glossterm>-exts</glossterm>
+            <glossdef>
+                <para>Defines a list of extensions to the given specification to export. Every
+                    argument that doesn't start with a "-" following this option will be assumed to
+                    be an extension name. You do not need to prefix the extensions with GL_, WGL_,
+                    or GLX_, but you may do so if you wish.</para>
+                <para>This argument can be specified multiple times. It is fine to specify an
+                    extension name more than once.</para>
+            </glossdef>
+        </glossentry>
+        <glossentry>
+            <glossterm>-ext</glossterm>
+            <glossdef>
+                <para>Defines a single extension to export. It adds the given parameter to the list
+                    of extensions.</para>
+                <para>This argument can be specified multiple times. It is fine to specify an
+                    extension name more than once.</para>
+            </glossdef>
+        </glossentry>
+        <glossentry>
+            <glossterm>-extfile</glossterm>
+            <glossdef>
+                <para>Specifying dozens of extensions on the command line can be exceedingly
+                    tedious. Therefore, the system can be instructed to read a list of extensions
+                    from a file with this option. The file should be a plain text file, where each
+                    extension is specified on a single line.</para>
+                <para>This argument can be specified multiple times. It is fine to specify an
+                    extension name more than once, either in the file or on the command line.</para>
+                <para>The file's directory is relative to the path where the command line was
+                    invoked.</para>
+            </glossdef>
+        </glossentry>
+        <glossentry>
+            <glossterm>-stdext</glossterm>
+            <glossdef>
+                <para>Works like <literal>extfile</literal>, except that the directory for the file
+                    is relative to the place where the <filename>LoadGen.lua</filename> file
+                    is.</para>
+            </glossdef>
+        </glossentry>
+    </glosslist>
+</article>

File docs/Extension Files.xml

-<?xml version="1.0" encoding="UTF-8"?>
-<?oxygen RNGSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng" type="xml"?>
-<?oxygen SCHSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng"?>
-<article xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
-    xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
-    <title>Extension Files</title>
-    <para>The extension file format is pretty simple, but it does have quite a bit of power to
-        it.</para>
-    <para>Every line of the file is expected to be one of the following:</para>
-    <itemizedlist>
-        <listitem>
-            <para>Nothing. An empty line, spaces, anything that isn't visible text.</para>
-        </listitem>
-        <listitem>
-            <para>A <literal>#include ""</literal> statement. This will cause the loading of another
-                extension file named in the <literal>""</literal>s. The <emphasis>current file's
-                    location</emphasis> will be the base directory for any relative paths. So if you
-                do <literal>#include "more.txt"</literal>, it will search for
-                    <filename>more.txt</filename> in the same directory as this extension
-                file.</para>
-        </listitem>
-        <listitem>
-            <para>A <literal>#include &lt;></literal> statement. This will cause the loading of
-                another extension file named in the <literal>&lt;></literal>s. The location of the
-                glLoadGen will be used for the base directory of any relative paths. This is mostly
-                intended to allow easy inclusion of the standard extension files, located in the
-                    <filename>extfiles</filename> directory. Therefore, </para>
-        </listitem>
-        <listitem>
-            <para>Anything starting with <literal>//</literal> will be ignored as a comment.</para>
-        </listitem>
-        <listitem>
-            <para>Anything starting with <literal>--</literal> will be ignored as a comment.</para>
-        </listitem>
-        <listitem>
-            <para>Any other text in a line will be interpreted as an extension name. Extension names
-                should not have the <quote>GL_</quote>/<quote>WGL_</quote>/<quote>GLX_</quote>
-                prefixes.</para>
-        </listitem>
-    </itemizedlist>
-    <para>The inclusion mechanism is quite powerful.</para>
-</article>

File docs/Extension_Files.xml

+<?xml version="1.0" encoding="UTF-8"?>
+<?oxygen RNGSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng" type="xml"?>
+<?oxygen SCHSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng"?>
+<article xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
+    xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
+    <title>Extension Files</title>
+    <para>The extension file format is pretty simple, but it does have quite a bit of power to
+        it.</para>
+    <para>Every line of the file is expected to be one of the following:</para>
+    <itemizedlist>
+        <listitem>
+            <para>Nothing. An empty line, spaces, anything that isn't visible text.</para>
+        </listitem>
+        <listitem>
+            <para>A <literal>#include ""</literal> statement. This will cause the loading of another
+                extension file named in the <literal>""</literal>s. The <emphasis>current file's
+                    location</emphasis> will be the base directory for any relative paths. So if you
+                do <literal>#include "more.txt"</literal>, it will search for
+                    <filename>more.txt</filename> in the same directory as this extension
+                file.</para>
+        </listitem>
+        <listitem>
+            <para>A <literal>#include &lt;></literal> statement. This will cause the loading of
+                another extension file named in the <literal>&lt;></literal>s. The location of the
+                glLoadGen will be used for the base directory of any relative paths. This is mostly
+                intended to allow easy inclusion of the standard extension files, located in the
+                    <filename>extfiles</filename> directory. Therefore, </para>
+        </listitem>
+        <listitem>
+            <para>Anything starting with <literal>//</literal> will be ignored as a comment.</para>
+        </listitem>
+        <listitem>
+            <para>Anything starting with <literal>--</literal> will be ignored as a comment.</para>
+        </listitem>
+        <listitem>
+            <para>Any other text in a line will be interpreted as an extension name. Extension names
+                should not have the <quote>GL_</quote>/<quote>WGL_</quote>/<quote>GLX_</quote>
+                prefixes.</para>
+        </listitem>
+    </itemizedlist>
+    <para>The inclusion mechanism is quite powerful.</para>
+</article>

File docs/Load Docs.xpr

                                     <String xml:space="preserve">XSL</String>
                                 </field>
                                 <field name="url">
-                                    <String xml:space="preserve">Extension%20Files.xml</String>
+                                    <String xml:space="preserve">Style_Pointer_C.xml</String>
                                 </field>
                             </scenarioAssociation>
                             <scenarioAssociation>
                                     <String xml:space="preserve">XSL</String>
                                 </field>
                                 <field name="url">
-                                    <String xml:space="preserve">Command%20Line%20Options.xml</String>
+                                    <String xml:space="preserve">Extension_Files.xml</String>
+                                </field>
+                            </scenarioAssociation>
+                            <scenarioAssociation>
+                                <field name="name">
+                                    <String xml:space="preserve">ToCreole</String>
+                                </field>
+                                <field name="type">
+                                    <String xml:space="preserve">XSL</String>
+                                </field>
+                                <field name="url">
+                                    <String xml:space="preserve">Command_Line_Options.xml</String>
+                                </field>
+                            </scenarioAssociation>
+                            <scenarioAssociation>
+                                <field name="name">
+                                    <String xml:space="preserve">ToCreole</String>
+                                </field>
+                                <field name="type">
+                                    <String xml:space="preserve">XSL</String>
+                                </field>
+                                <field name="url">
+                                    <String xml:space="preserve">ToCreole.xsl</String>
+                                </field>
+                            </scenarioAssociation>
+                            <scenarioAssociation>
+                                <field name="name">
+                                    <String xml:space="preserve">ToCreole</String>
+                                </field>
+                                <field name="type">
+                                    <String xml:space="preserve">XSL</String>
+                                </field>
+                                <field name="url">
+                                    <String xml:space="preserve">Extension%20Files.xml</String>
                                 </field>
                             </scenarioAssociation>
                             <scenarioAssociation>
                                     <String xml:space="preserve">XSL</String>
                                 </field>
                                 <field name="url">
-                                    <String xml:space="preserve">ToCreole.xsl</String>
+                                    <String xml:space="preserve">Command%20Line%20Options.xml</String>
                                 </field>
                             </scenarioAssociation>
                             <scenarioAssociation>
             <file name="TagsToSupport.txt"/>
             <file name="ToCreole.xsl"/>
         </folder>
+        <file name="Command_Line_Options.xml"/>
+        <file name="Extension_Files.xml"/>
         <file name="Home.xml"/>
+        <file name="Style_Pointer_C.xml"/>
         <file name="Styles.xml"/>
     </projectTree>
 </project>

File docs/Style Pointer C.xml

-<?xml version="1.0" encoding="UTF-8"?>
-<?oxygen RNGSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng" type="xml"?>
-<?oxygen SCHSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng"?>
-<article xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
-    xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
-    <title>Style Pointer C</title>
-    <para>The <literal>pointer_c</literal> style is the default style. It is also the one that most
-        mimics the way common OpenGL loaders work. This style generates a <filename>.h</filename>
-        and <filename>.c</filename> file. The header file can be included by C and C++; the source
-        file should be compiled as C.</para>
-    <para>Since these are compatible with C, all of the typedefs, enumerations, extension variables,
-        and function pointers are global. The extension variables are of type
-        <literal>int</literal>. Enumerations are <literal>#define</literal>s. The functions are
-        function pointers with mangled names that have been <literal>#define</literal>d into the
-        real OpenGL function name. The latter is done to avoid name conflicts with static linking of
-        certain core OpenGL function names.</para>
-    <para>The loading function that loads the extensions and OpenGL version is called
-            <literal>LoadFunction</literal>, prefixed by a specification-specific prefix. The return
-        value of this function, as well as the value stored in the extension variables, is special.
-        There is an enumeration, prefixed again by the spec-specific prefix.</para>
-    <para>If the value is <literal>LOAD_FAILED</literal>, then the extension was not found in the
-        extension string, so no attempt was made to load it. If the value is
-            <literal>LOAD_SUCCEEDED</literal>, then the extension was loaded in its entirety (all
-        function pointers accounted for). Otherwise, some number of function pointers failed to
-        load. To get the number of functions that failed to load for the extension, take the integer
-        value and subtract <literal>LOAD_SUCCEEDED</literal> from it.</para>
-    <para>The return value for the function loader works the same way. It refers to the success or
-        failure to load the core functions (obviously for WGL/GLX, there are no core functions, so
-        it will always be successful). The attempt will always be made to load the core functions,
-        so <literal>LOAD_FAILED</literal> is not a possibility.</para>
-    <para>Also, this style will generate functions to query version availability for core OpenGL. </para>
-    <section>
-        <title>Compatibility</title>
-        <para>This style is intended to be maximally compatible with regular OpenGL programs. You
-            should be able to take this header and include it into a standard GL program and use it
-            as is. Furthermore, it should be compatible with other systems like FreeGLUT, GLFW, and
-            so forth, as it provides information in the way that traditional OpenGL headers
-            do.</para>
-        <para>However, in all cases, you should include these generated headers
-                <emphasis>before</emphasis> anything from FreeGLUT, GLFW, etc.</para>
-    </section>
-</article>

File docs/Style_Pointer_C.xml

+<?xml version="1.0" encoding="UTF-8"?>
+<?oxygen RNGSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng" type="xml"?>
+<?oxygen SCHSchema="http://docbook.org/xml/5.0/rng/docbookxi.rng"?>
+<article xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
+    xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
+    <title>Style Pointer C</title>
+    <para>The <literal>pointer_c</literal> style is the default style. It is also the one that most
+        mimics the way common OpenGL loaders work. This style generates a <filename>.h</filename>
+        and <filename>.c</filename> file. The header file can be included by C and C++; the source
+        file should be compiled as C.</para>
+    <para>Since these are compatible with C, all of the typedefs, enumerations, extension variables,
+        and function pointers are global. The extension variables are of type
+        <literal>int</literal>. Enumerations are <literal>#define</literal>s. The functions are
+        function pointers with mangled names that have been <literal>#define</literal>d into the
+        real OpenGL function name. The latter is done to avoid name conflicts with static linking of
+        certain core OpenGL function names.</para>
+    <para>The loading function that loads the extensions and OpenGL version is called
+            <literal>LoadFunction</literal>, prefixed by a specification-specific prefix. The return
+        value of this function, as well as the value stored in the extension variables, is special.
+        There is an enumeration, prefixed again by the spec-specific prefix.</para>
+    <para>If the value is <literal>LOAD_FAILED</literal>, then the extension was not found in the
+        extension string, so no attempt was made to load it. If the value is
+            <literal>LOAD_SUCCEEDED</literal>, then the extension was loaded in its entirety (all
+        function pointers accounted for). Otherwise, some number of function pointers failed to
+        load. To get the number of functions that failed to load for the extension, take the integer
+        value and subtract <literal>LOAD_SUCCEEDED</literal> from it.</para>
+    <para>The return value for the function loader works the same way. It refers to the success or
+        failure to load the core functions (obviously for WGL/GLX, there are no core functions, so
+        it will always be successful). The attempt will always be made to load the core functions,
+        so <literal>LOAD_FAILED</literal> is not a possibility.</para>
+    <para>Also, this style will generate functions to query version availability for core OpenGL. </para>
+    <section>
+        <title>Compatibility</title>
+        <para>This style is intended to be maximally compatible with regular OpenGL programs. You
+            should be able to take this header and include it into a standard GL program and use it
+            as is. Furthermore, it should be compatible with other systems like FreeGLUT, GLFW, and
+            so forth, as it provides information in the way that traditional OpenGL headers
+            do.</para>
+        <para>However, in all cases, you should include these generated headers
+                <emphasis>before</emphasis> anything from FreeGLUT, GLFW, etc.</para>
+    </section>
+</article>