/usr/lib/swi-prolog/doc/Manual/guidelines.html

<!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.7</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="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;
}

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="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 class="latex">
<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 &lt;=&gt; 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:1364"></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>
swi-prolog-nox 5.10.4-3ubuntu1 / usr / lib / swi-prolog / doc / Manual / guidelines.html
