This file is indexed.

/usr/share/doc/cl-uffi/html/object-represen.html is in cl-uffi 2.1.2-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Foreign Object Representation and Access</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><link rel="home" href="index.html" title="UFFI Reference Guide" /><link rel="up" href="notes.html" title="Chapter 2. Programming Notes" /><link rel="prev" href="notes.html" title="Chapter 2. Programming Notes" /><link rel="next" href="optimizing.html" title="Optimizing Code Using UFFI" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Foreign Object Representation and Access</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="notes.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Programming Notes</th><td width="20%" align="right"> <a accesskey="n" href="optimizing.html">Next</a></td></tr></table><hr /></div><div class="sect1" title="Foreign Object Representation and Access"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="object-represen"></a>Foreign Object Representation and Access</h2></div></div></div><p> There are two main approaches used to represent foreign
    objects: an integer that represents an address in memory, and a
    object that also includes run-time typing. The advantage of
    run-time typing is the system can dereference pointers and perform
    array access without those functions requiring a type at the cost
    of additional overhead to generate and store the run-time
    typing. The advantage of integer representation, at least for
    <span class="application">AllegroCL</span>, is that the compiler can generate inline code to
    dereference pointers. Further, the overhead of the run-time type
    information is eliminated. The disadvantage is the program must
    then supply
    the type to the functions to dereference objects and array.
    </p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="notes.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="notes.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="optimizing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Programming Notes </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Optimizing Code Using UFFI</td></tr></table></div></body></html>