Update AllegroCL for :long-long on 64-bit platforms

[uffi.git] / doc / notes.xml

diff --git a/doc/notes.xml b/doc/notes.xml
index a492c2d348d5bdd48ec69e91e48a9da68edab7a8..5678588f5ca058cd3e54b992e96a4986a2c01780 100644 (file)
--- a/doc/notes.xml
+++ b/doc/notes.xml
@@ -1,9 +1,14 @@
-<?xml version='1.0' ?>   <!-- Mode: Docbook --> 
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+               "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+<!ENTITY % myents SYSTEM "entities.inc">
+%myents;
+]>
 
 <chapter id="notes">
   <title>Programming Notes</title>
 
-  <sect1>
+  <sect1 id="impl-specific">
     <title>Implementation Specific Notes</title> 
     <para>
     </para>
@@ -24,7 +29,7 @@
       </sect2>
   </sect1>
 
-  <sect1>
+  <sect1 id="object-represen">
     <title>Foreign Object Representation and Access</title>
     <para> There are two main approaches used to represent foreign
     objects: an integer that represents an address in memory, and a
@@ -41,7 +46,7 @@
     </para>
   </sect1>
 
-  <sect1>
+  <sect1 id="optimizing">
     <title>Optimizing Code Using UFFI</title>
     <sect2>
       <title>Background</title>
@@ -76,12 +81,12 @@
       <para>
        Here is an example that should both methods being used for
        maximum cross-implementation optimization:
-       <programlisting>
+       <screen>
 (uffi:def-type the-struct-type-def the-struct-type)
 (let ((a-foreign-struct (allocate-foreign-object 'the-struct-type)))
   (declare 'the-struct-type-def a-foreign-struct)
   (get-slot-value a-foreign-struct 'the-struct-type 'field-name))
-       </programlisting>
+       </screen>
       </para>
     </sect2>
   </sect1>