/usr/share/doc/swi-prolog-doc/Manual/guidelines.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 | <!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: Section 7.7</TITLE><LINK REL=home HREF="index.html">
<LINK REL=contents HREF="Contents.html">
<LINK REL=index HREF="DocIndex.html">
<LINK REL=previous HREF="sicstus-chr.html">
<LINK REL=next HREF="errors.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="sicstus-chr.html"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A class="nav" href="errors.html"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
</DIV>
<H2><A NAME="sec:7.7"><SPAN class="sec-nr">7.7</SPAN> <SPAN class="sec-title">Programming
Tips and Tricks</SPAN></A></H2>
<A NAME="sec:guidelines"></A> In this section we cover several
guidelines on how to use CHR to write constraint solvers and how to do
so efficiently.
<P>
<UL>
<LI><I>Check guard bindings yourself</I><BR>
It is considered bad practice to write guards that bind variables of the
head and to rely on the system to detect this at runtime. It is
inefficient and obscures the working of the program.
<P>
<LI><I>Set semantics</I><BR>
The CHR system allows the presence of identical constraints, i.e.
multiple constraints with the same functor, arity and arguments. For
most constraint solvers, this is not desirable: it affects efficiency
and possibly termination. Hence appropriate simpagation rules should be
added of the form: [ constraint <CODE>\</CODE>constraint <=> true ]
<P>
<LI><I>Multi-headed rules</I><BR>
Multi-headed rules are executed more efficiently when the constraints
share one or more variables.
<P>
<LI><I>Mode and type declarations</I><BR>
Provide mode and type declarations to get more efficient program
execution. Make sure to disable debug (-nodebug) and enable optimization
(-O).
<P>
<LI><I>Compile once, run many times</I><BR>
Does consulting your CHR program take a long time in SWI-Prolog?
Probably it takes the CHR compiler a long time to compile the CHR rules
into Prolog code. When you disable optimizations the CHR compiler will
be a lot quicker, but you may loose performance. Alternatively, you can
just use SWI-Prolog's
<A NAME="idx:qcompile1:1262"></A><A class="pred" href="consulting.html#qcompile/1">qcompile/1</A>
to generate a <CODE>.qlf</CODE> file once from your
<CODE>.pl</CODE> file. This <CODE>.qlf</CODE> contains the generated
code of the CHR compiler (be it in a binary format). When you consult
the <CODE>.qlf</CODE> file, the CHR compiler is not invoked and
consultation is much faster.
<P>
<LI><I>Finding Constraints</I><BR>
The <A class="pred" href="debugging.html#find_chr_constraint/1">find_chr_constraint/1</A>
predicate is fairly expensive. Avoid it, if possible. If you must use
it, try to use it with an instantiated toplevel constraint symbol.
</UL>
<P></BODY></HTML>
|