This file is indexed.

/usr/share/doc/swi-prolog-doc/Manual/dialect.html is in swi-prolog-doc 5.6.59-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
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<HTML>
<HEAD>
<TITLE>SWI-Prolog 5.6.59 Reference Manual</TITLE><LINK REL=home HREF="index.html">
<LINK REL=contents HREF="Contents.html">
<LINK REL=index HREF="DocIndex.html">
<LINK REL=previous HREF="readline.html">
<LINK REL=next HREF="portabilitystrategies.html">
<STYLE type="text/css">
/* Style sheet for SWI-Prolog latex2html
*/

dd.defbody
{ margin-bottom: 1em;
}

dt.pubdef
{ background-color: #c5e1ff;
}

pre.code
{ margin-left: 1.5em;
margin-right: 1.5em;
border: 1px dotted;
padding-top: 5px;
padding-left: 5px;
padding-bottom: 5px;
background-color: #f8f8f8;
}

div.navigate
{ text-align: center;
background-color: #f0f0f0;
border: 1px dotted;
padding: 5px;
}

div.title
{ text-align: center;
padding-bottom: 1em;
font-size: 200%;
font-weight: bold;
}

div.author
{ text-align: center;
font-style: italic;
}

div.abstract
{ margin-top: 2em;
background-color: #f0f0f0;
border: 1px dotted;
padding: 5px;
margin-left: 10%; margin-right:10%;
}

div.abstract-title
{ text-align: center;
padding: 5px;
font-size: 120%;
font-weight: bold;
}

div.toc-h1
{ font-size: 200%;
font-weight: bold;
}

div.toc-h2
{ font-size: 120%;
font-weight: bold;
margin-left: 2em;
}

div.toc-h3
{ font-size: 100%;
font-weight: bold;
margin-left: 4em;
}

div.toc-h4
{ font-size: 100%;
margin-left: 6em;
}

span.sec-nr
{ 
}

span.sec-title
{ 
}

span.pred-ext
{ font-weight: bold;
}

span.pred-tag
{ float: right;
font-size: 80%;
font-style: italic;
color: #202020;
}

/* Footnotes */

sup.fn { color: blue; text-decoration: underline; }
span.fn-text { display: none; }
sup.fn span {display: none;}
sup:hover span 
{ display: block !important;
position: absolute; top: auto; left: auto; width: 80%;
color: #000; background: white;
border: 2px solid;
padding: 5px; margin: 10px; z-index: 100;
font-size: smaller;
}
</STYLE>
</HEAD>
<BODY BGCOLOR="white">
<DIV class="navigate"><A class="nav" href="index.html"><IMG SRC="home.gif" BORDER=0 ALT="Home"></A>
<A class="nav" href="Contents.html"><IMG SRC="index.gif" BORDER=0 ALT="Contents"></A>
<A class="nav" href="DocIndex.html"><IMG SRC="yellow_pages.gif" BORDER=0 ALT="Index"></A>
<A class="nav" href="readline.html"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A class="nav" href="portabilitystrategies.html"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
</DIV>

<H1><A NAME="sec:C"><SPAN class="sec-nr">C</SPAN> <SPAN class="sec-title">Compatibility 
with other Prolog dialects</SPAN></A></H1>

<A NAME="sec:dialect"></A>

<P><A NAME="idx:YAPprolog:1588"></A><A NAME="idx:portableprologcode:1589"></A>This 
chapter explains issues for writing portable Prolog programs. It was 
started after discussion with Vitor Santos Costa, the leading developer 
of YAP Prolog<SUP class="fn">90<SPAN class="fn-text"><A class="url" href="http://yap.sourceforge.net/">http://yap.sourceforge.net/</A></SPAN></SUP> 
YAP and SWI-Prolog have expressed the ambition to enhance the 
portability beyond the trivial Prolog examples, including complex 
libraries involving foreign code.

<P>Although it is our aim to enhance compatibility, we are still faced 
with many incompatibilities between the dialects. As a first step both 
YAP and SWI will provide some instruments that help developing portable 
code. A first release of these tools appeared in SWI-Prolog 5.6.43. Some 
of the facilities are implemented in the base system. Others in the 
library <CODE>library(dialect.pl)</CODE>.

<P>
<UL>
<LI>The Prolog flag <A class="flag" href="flags.html#flag:dialect">dialect</A> 
is an unambiguous and fast way to find out which Prolog dialect executes 
your program. It has the value <CODE>swi</CODE> for SWI-Prolog and <CODE>yap</CODE> 
on YAP.

<P>
<LI>The Prolog flag <A class="flag" href="flags.html#flag:version_data">version_data</A> 
is bound to a term
<CODE>swi(Major, Minor, Patch, Extra)</CODE>

<P>
<LI>Conditional compilation using <CODE>:- if(Condition)</CODE> ...<CODE>:- 
endif</CODE> is supported. See <A class="sec" href="consulting.html">section 
4.3.1.1</A>.

<P>
<LI>The predicate <A NAME="idx:expectsdialect1:1590"></A><A class="pred" href="dialect.html#expects_dialect/1">expects_dialect/1</A> 
allows for specifying for which Prolog system the code was written.

<P>
<LI>The predicates <A NAME="idx:existssource1:1591"></A><A class="pred" href="dialect.html#exists_source/1">exists_source/1</A> 
and <A NAME="idx:sourceexports2:1592"></A><A class="pred" href="dialect.html#source_exports/2">source_exports/2</A> 
can be used to query the library content. The <A NAME="idx:require1:1593"></A><A class="pred" href="consulting.html#require/1">require/1</A> 
directive can be used to get access to predicates without knowing their 
location.

<P>
<LI>The module predicates <A NAME="idx:usemodule1:1594"></A><A class="pred" href="import.html#use_module/1">use_module/1</A>, <A NAME="idx:usemodule2:1595"></A><A class="pred" href="import.html#use_module/2">use_module/2</A> 
have been extended with a notion for `import-except' and `import-as'. 
This is particulary useful together with <A NAME="idx:reexport1:1596"></A><A class="pred" href="reexport.html#reexport/1">reexport/1</A> 
and <A NAME="idx:reexport2:1597"></A><A class="pred" href="reexport.html#reexport/2">reexport/2</A> 
to compose modules from other modules and mapping names.

<P>
<LI>Foreign code can expect <CODE>__SWI_PROLOG__</CODE> when compiled 
for SWI-Prolog and <CODE>__YAP_PROLOG__</CODE> when compiled on YAP.
</UL>

<DL>
<DT class="pubdef"><A NAME="expects_dialect/1">:- <STRONG>expects_dialect</STRONG>(<VAR>+Dialect</VAR>)</A></DT>
<DD class="defbody">
This directive states that the code following the directive is written 
for the given Prolog <VAR>Dialect</VAR>. See also <A class="flag" href="flags.html#flag:dialect">dialect</A>. 
The declaration holds until the end of the file in which it appears. The 
current dialect is available using <A NAME="idx:prologloadcontext2:1598"></A><A class="pred" href="consulting.html#prolog_load_context/2">prolog_load_context/2</A>.

<P>The exact behaviour of this predicate is still subject to discussion. 
Of course, if <VAR>Dialect</VAR> matches the running dialect the 
directive has no effect. Otherwise we check for the existence of
<CODE>library(dialect/Dialect)</CODE> and load it if the file is found. 
Currently, this file has this functionality:

<P>
<UL>
<LI>Define system predicates of the requested dialect we do not have.

<P>
<LI>Apply <A NAME="idx:goalexpansion2:1599"></A><A class="pred" href="consulting.html#goal_expansion/2">goal_expansion/2</A> 
rules that map conflicting predicates to versions emulating the 
requested dialect. These expansion rules reside in the dialect 
compatibility module, but are applied if prolog_load_context(dialect, 
Dialect) is active.

<P>
<LI>Modify the search path for library directories, putting libraries 
compatible to the target dialect before the native libraries.

<P>
<LI>Setup support for the default filename extension of the dialect.
</UL>
</DD>
<DT class="pubdef"><A NAME="exists_source/1"><STRONG>exists_source</STRONG>(<VAR>+Spec</VAR>)</A></DT>
<DD class="defbody">
Is true if <VAR>Spec</VAR> exists as a Prolog source. <VAR>Spec</VAR> 
uses the same conventions as <A NAME="idx:loadfiles2:1600"></A><A class="pred" href="consulting.html#load_files/2">load_files/2</A>. 
Fails without error if <VAR>Spec</VAR> cannot be found.</DD>
<DT class="pubdef"><A NAME="source_exports/2"><STRONG>source_exports</STRONG>(<VAR>+Spec, 
+Export</VAR>)</A></DT>
<DD class="defbody">
Is true if source <VAR>Spec</VAR> exports <VAR>Export</VAR>, a predicate 
indicator. Fails without error otherwise.
</DD>
</DL>

<P>
<HR>
<CENTER>

<H2>Section Index</H2>

</CENTER>
<HR>
<DIV class="toc">
<DIV class="toc-h2"><A class="sec" href="portabilitystrategies.html"><SPAN class="sec-nr">C.1</SPAN> <SPAN class="sec-title">Some 
considerations for writing portable code</SPAN></A></DIV>
</DIV>
</BODY></HTML>