/usr/lib/swi-prolog/doc/Manual/sicstus-chr.html is in swi-prolog-nox 5.10.4-3ubuntu1.
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 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<HTML>
<HEAD>
<TITLE>SWI-Prolog 5.11.18 Reference Manual: Section 7.6</TITLE><LINK REL=home HREF="index.html">
<LINK REL=contents HREF="Contents.html">
<LINK REL=index HREF="DocIndex.html">
<LINK REL=summary HREF="summary.html">
<LINK REL=previous HREF="examples.html">
<LINK REL=next HREF="guidelines.html">
<STYLE type="text/css">
/* Style sheet for SWI-Prolog latex2html
*/
dd.defbody
{ margin-bottom: 1em;
}
dt.pubdef
{ background-color: #c5e1ff;
}
dt.multidef
{ background-color: #c8ffc7;
}
.bib dd
{ margin-bottom: 1em;
}
.bib dt
{ float: left;
margin-right: 1.3ex;
}
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;
padding-top: 0.2em;
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="summary.html"><IMG SRC="info.gif" BORDER=0 ALT="Summary"></A>
<A class="nav" href="examples.html"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A class="nav" href="guidelines.html"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
</DIV>
<H2><A NAME="sec:7.6"><SPAN class="sec-nr">7.6</SPAN> <SPAN class="sec-title">Backwards
Compatibility</SPAN></A></H2>
<A NAME="sec:sicstus-chr"></A>
<H3><A NAME="sec:7.6.1"><SPAN class="sec-nr">7.6.1</SPAN> <SPAN class="sec-title">The
Old SICStus CHR implemenation</SPAN></A></H3>
<P>There are small differences between the current K.U.Leuven CHR system
in SWI-Prolog, older versions of the same system and SICStus' CHR
system.
<P>The current system maps old syntactic elements onto new ones and
ignores a number of no longer required elements. However, for each a <EM>deprecated</EM>
warning is issued. You are strongly urged to replace or remove
deprecated features.
<P>Besides differences in available options and pragmas, the following
differences should be noted:
<P>
<UL class="latex">
<LI><I>The constraints/1 declaration</I><BR>
This declaration is deprecated. It has been replaced with the
<A NAME="idx:chrconstraint1:1361"></A><A class="pred" href="practical.html#chr_constraint/1">chr_constraint/1</A>
declaration.
<P>
<LI><I>The option/2 declaration</I><BR>
This declaration is deprecated. It has been replaced with the
<A NAME="idx:chroption2:1362"></A><A class="pred" href="SyntaxAndSemantics.html#chr_option/2">chr_option/2</A>
declaration.
<P>
<LI><I>The handler/1 declaration</I><BR>
In SICStus every CHR module requires a handler/1 declaration declaring a
unique handler name. This declaration is valid syntax in SWI-Prolog, but
will have no effect. A warning will be given during compilation.
<P>
<LI><I>The rules/1 declaration</I><BR>
In SICStus, for every CHR module it is possible to only enable a subset
of the available rules through the rules/1 declaration. The declaration
is valid syntax in SWI-Prolog, but has no effect. A warning is given
during compilation.
<P>
<LI><I>Guard bindings</I><BR>
The <TT>check_guard_bindings</TT> option only turns invalid calls to
unification into failure. In SICStus this option does more: it
intercepts instantiation errors from Prolog built-ins such as <A NAME="idx:is2:1363"></A><A class="pred" href="arith.html#is/2">is/2</A>
and turns them into failure. In SWI-Prolog, we do not go this far, as we
like to separate concerns more. The CHR compiler is aware of the CHR
code, the Prolog system and programmer should be aware of the
appropriate meaning of the Prolog goals used in guards and bodies of CHR
rules.
</UL>
<H3><A NAME="sec:7.6.2"><SPAN class="sec-nr">7.6.2</SPAN> <SPAN class="sec-title">The
Old ECLiPSe CHR implemenation</SPAN></A></H3>
<P>The old ECLiPSe CHR implementations features a label_with/1 construct
for labeling variables in CHR constraints. This feature has long since
been abandoned. However, a simple transformation is all that is required
to port the functionality.
<PRE class="code">
label_with Constraint1 if Condition1.
...
label_with ConstraintN if ConditionN.
Constraint1 :- Body1.
...
ConstraintN :- BodyN.
</PRE>
<P>is transformed into
<PRE class="code">
:- chr_constraint my_labeling/0.
my_labeling \ Constraint1 <=> Condition1 | Body1.
...
my_labeling \ ConstraintN <=> ConditionN | BodyN.
my_labeling <=> true.
</PRE>
<P>Be sure to put this code after all other rules in your program! With
my_labeling/0 (or another predicate name of your choosing) the labeling
is initiated, rather than ECLiPSe's chr_labeling/0 .
<P></BODY></HTML>
|