<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://groups.google.at/group/comp.lang.prolog</id>
  <title type="text">comp.lang.prolog Google Group</title>
  <subtitle type="text">
  Discussion about PROLOG.
  </subtitle>
  <link href="/group/comp.lang.prolog/feed/atom_v1_0_msgs.xml" rel="self" title="comp.lang.prolog feed"/>
  <updated>2010-03-18T13:41:32Z</updated>
  <generator uri="http://groups.google.at" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Ulrich Neumerkel</name>
  <email>ulr...@mips.complang.tuwien.ac.at</email>
  </author>
  <updated>2010-03-18T13:41:32Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/81deddbd7baaed23/a57c23477bb2fab7?show_docid=a57c23477bb2fab7</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/81deddbd7baaed23/a57c23477bb2fab7?show_docid=a57c23477bb2fab7"/>
  <title type="text">Re: Lambdas in Prolog</title>
  <summary type="html" xml:space="preserve">
  To facilitate the inclusion of library(lambda) into Prolog systems &lt;br&gt; the two-clause BSD license has been added: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.complang.tuwien.ac.at/ulrich/Prolog-inedit/lambda.pl&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jan Wielemaker</name>
  <email>j...@hppc323.few.vu.nl</email>
  </author>
  <updated>2010-03-18T08:50:42Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/ad5c2261d7950855?show_docid=ad5c2261d7950855</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/ad5c2261d7950855?show_docid=ad5c2261d7950855"/>
  <title type="text">Re: Quintus --&gt; Sicstus</title>
  <summary type="html" xml:space="preserve">
  It helps if you post the code fragment and the error message. Someone &lt;br&gt; is likely to be able to help you with proper advice. &lt;br&gt; --- Jan
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jan Burse</name>
  <email>janbu...@fastmail.fm</email>
  </author>
  <updated>2010-03-18T00:26:24Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/bb43d67221992d41?show_docid=bb43d67221992d41</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/bb43d67221992d41?show_docid=bb43d67221992d41"/>
  <title type="text">Re: Quintus --&gt; Sicstus</title>
  <summary type="html" xml:space="preserve">
  Ulrich Neumerkel schrieb: &lt;br&gt; Here you go, I guess this is done view list_undefined/0. &lt;br&gt; From the definition of this predicate I conclude that &lt;br&gt; it will not detect predicates which will become implicitly &lt;br&gt; dynamic by means of asserta/1 or assertz/1 during program &lt;br&gt; execution (as by the ISO standard). &lt;br&gt; Even if the asserta/1 or assertz/1 does not use a
  </summary>
  </entry>
  <entry>
  <author>
  <name>zslevi</name>
  <email>zsl...@gmail.com</email>
  </author>
  <updated>2010-03-18T00:14:48Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/a76558e582376d99/e2640a9ccb93dba3?show_docid=e2640a9ccb93dba3</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/a76558e582376d99/e2640a9ccb93dba3?show_docid=e2640a9ccb93dba3"/>
  <title type="text">Re: write a prolog interpreter in prolog (ala Lisp)</title>
  <summary type="html" xml:space="preserve">
  I refined it a bit &lt;br&gt; interpret(&#39;,&#39;(A,!)):- &lt;br&gt; interpret(A),!. &lt;br&gt; interpret(&#39;,&#39;(!,A)):- &lt;br&gt; !,interpret(A). &lt;br&gt; interpret(&#39;,&#39;(A1,A2)):- &lt;br&gt; !,(interpret(A1),interpret(A2) ). &lt;br&gt; interpret(&#39;;&#39;(A1,A2)):- &lt;br&gt; !,(interpret(A1);interpret(A2) ). &lt;br&gt; interpret(&#39;-&amp;gt;&#39;(A1,A2)):- &lt;br&gt; !, interpret(A1) -&amp;gt; interpret(A2). &lt;br&gt; /* &lt;br&gt; interpret(X):-
  </summary>
  </entry>
  <entry>
  <author>
  <name>Ulrich Neumerkel</name>
  <email>ulr...@mips.complang.tuwien.ac.at</email>
  </author>
  <updated>2010-03-17T23:01:13Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/a76558e582376d99/4171fa8ead3703e3?show_docid=4171fa8ead3703e3</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/a76558e582376d99/4171fa8ead3703e3?show_docid=4171fa8ead3703e3"/>
  <title type="text">Re: write a prolog interpreter in prolog (ala Lisp)</title>
  <summary type="html" xml:space="preserve">
  You have to cut out of a disjunction to make ! work. Otherwise, you &lt;br&gt; can implement ! via catch/3 and throw/1 - not the most efficient way, &lt;br&gt; though. The (-&amp;gt;)/2 would need special attention too.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Ulrich Neumerkel</name>
  <email>ulr...@mips.complang.tuwien.ac.at</email>
  </author>
  <updated>2010-03-17T22:59:11Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/a39c8627c578ff90?show_docid=a39c8627c578ff90</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/a39c8627c578ff90?show_docid=a39c8627c578ff90"/>
  <title type="text">Re: Quintus --&gt; Sicstus</title>
  <summary type="html" xml:space="preserve">
  In SWI, you load your files. Then you say make/0 to get undefined predicates &lt;br&gt; listed.
  </summary>
  </entry>
  <entry>
  <author>
  <name>nev</name>
  <email></email>
  </author>
  <updated>2010-03-17T22:38:22Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/478bc643bc4f039f?show_docid=478bc643bc4f039f</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/478bc643bc4f039f?show_docid=478bc643bc4f039f"/>
  <title type="text">Re: Quintus --&gt; Sicstus</title>
  <summary type="html" xml:space="preserve">
  Is there a solution to catch &amp;quot;existence error&#39;s&amp;quot; in &amp;quot;compile time&amp;quot;? (I know &lt;br&gt; this is not precise wording in the case of Prolog) &lt;br&gt; I have very much old files (from 1982), some of them tries override the &lt;br&gt; system&#39;s predicates, eg. I/O operations, arithmetics. Sometimes the compiler &lt;br&gt; puts a &amp;quot;permission error&amp;quot;, but not allways. And if I delete something
  </summary>
  </entry>
  <entry>
  <author>
  <name>zslevi</name>
  <email>zsl...@gmail.com</email>
  </author>
  <updated>2010-03-17T21:19:31Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/a76558e582376d99/fa1a31309457f4c8?show_docid=fa1a31309457f4c8</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/a76558e582376d99/fa1a31309457f4c8?show_docid=fa1a31309457f4c8"/>
  <title type="text">write a prolog interpreter in prolog (ala Lisp)</title>
  <summary type="html" xml:space="preserve">
  I tried the following, but it didn&#39;t handle cut correctly (I guess, &lt;br&gt; because it makes separate frame for everything): &lt;br&gt; interpret(&#39;,&#39;(A,!)):- &lt;br&gt; interpret(A),!. &lt;br&gt; interpret(&#39;,&#39;(!,A)):- &lt;br&gt; !,interpret(A). &lt;br&gt; interpret(&#39;,&#39;(A1,A2)):- &lt;br&gt; !,(interpret(A1),interpret(A2) ). &lt;br&gt; interpret(&#39;;&#39;(A1,A2)):- &lt;br&gt; !,(interpret(A1);interpret(A2) ).
  </summary>
  </entry>
  <entry>
  <author>
  <name>bart demoen</name>
  <email>b...@cs.kuleuven.be</email>
  </author>
  <updated>2010-03-17T21:02:03Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/680992f4dfabbb00/8a43e7aa13e677e6?show_docid=8a43e7aa13e677e6</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/680992f4dfabbb00/8a43e7aa13e677e6?show_docid=8a43e7aa13e677e6"/>
  <title type="text">Re: dcg question from Learn Prolog Now</title>
  <summary type="html" xml:space="preserve">
  No you don&#39;t - the answer is different, but it is printed out the same &lt;br&gt; because the default settings for printing are such that they LOOK the &lt;br&gt; same - try w instead of ; &lt;br&gt; And if your Prolog systems does not produce answers like &lt;br&gt; X = [the, woman, shoots, the, woman, and, the, woman, shoots, the, woman, &lt;br&gt; and, the, woman, shoots, the, woman, and, a, woman, shoots, the, man] .
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jan Burse</name>
  <email>janbu...@fastmail.fm</email>
  </author>
  <updated>2010-03-17T19:56:26Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/66cc95585107b13a?show_docid=66cc95585107b13a</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/66cc95585107b13a?show_docid=66cc95585107b13a"/>
  <title type="text">Re: Quintus --&gt; Sicstus</title>
  <summary type="html" xml:space="preserve">
  Jan Wielemaker schrieb: &lt;br&gt; Yes and no. &lt;br&gt; So I am assuming some GC, so the original list goes &lt;br&gt; up like a little balloon, to the roof, when it is &lt;br&gt; not used anymore. &lt;br&gt; The list contains clauses, and these clauses might &lt;br&gt; have many uses, not only in choice points, but also &lt;br&gt; through instantiations when the choice point has
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jan Wielemaker</name>
  <email>j...@hppc323.few.vu.nl</email>
  </author>
  <updated>2010-03-17T19:41:19Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/9c77246946ae2761?show_docid=9c77246946ae2761</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/9c77246946ae2761?show_docid=9c77246946ae2761"/>
  <title type="text">Re: Quintus --&gt; Sicstus</title>
  <summary type="html" xml:space="preserve">
  Yes, but sooner or later you need to reclaim the old definition. I&#39;m &lt;br&gt; not really saying it cannot be done, but it is far from trivial. &lt;br&gt; No. No sensible system will inline dynamic predicates, but any &lt;br&gt; implementation should be allowed to inline static code at will. &lt;br&gt; development problems (re-consult does something like this), but
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jan Burse</name>
  <email>janbu...@fastmail.fm</email>
  </author>
  <updated>2010-03-17T19:00:38Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/349723958d18fd84/d9d6c3f5b2b5cdf0?show_docid=d9d6c3f5b2b5cdf0</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/349723958d18fd84/d9d6c3f5b2b5cdf0?show_docid=d9d6c3f5b2b5cdf0"/>
  <title type="text">Re: Prolog Incompletness (Was: Prolog&#39;s most illogical feature)</title>
  <summary type="html" xml:space="preserve">
  Jan Burse schrieb: &lt;br&gt; Just had an interesting finding (Michael Brady, &lt;br&gt; Open Prolog Thesis): &lt;br&gt; [..] &lt;br&gt; To enable the cut to handle NR frames efficiently, a &lt;br&gt; new OPAM register, the NR register, is introduced. &lt;br&gt; This register always points to the most recently &lt;br&gt; allocated NR frame. By comparing the cut frame &lt;br&gt; address with the NR register contents, the presence
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jan Burse</name>
  <email>janbu...@fastmail.fm</email>
  </author>
  <updated>2010-03-17T18:09:10Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/5e4fac83562b5b56?show_docid=5e4fac83562b5b56</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/f902c890fd60c74a/5e4fac83562b5b56?show_docid=5e4fac83562b5b56"/>
  <title type="text">Re: Quintus --&gt; Sicstus</title>
  <summary type="html" xml:space="preserve">
  Jan Wielemaker schrieb: &lt;br&gt; Well actually my experience is that the abolish in &lt;br&gt; a multi-threaded interpreter is not so much a problem &lt;br&gt; if you DO NOT implement it as some retract all. You &lt;br&gt; can in one shot throw away all clauses by setting the &lt;br&gt; clause list of the predicate to empty(*). Can be done &lt;br&gt; synchronized and should be very efficient, isn&#39;t it?
  </summary>
  </entry>
  <entry>
  <author>
  <name>metaperl</name>
  <email>scheme...@gmail.com</email>
  </author>
  <updated>2010-03-17T13:54:41Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/680992f4dfabbb00/d4d71922ac0a47ca?show_docid=d4d71922ac0a47ca</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/680992f4dfabbb00/d4d71922ac0a47ca?show_docid=d4d71922ac0a47ca"/>
  <title type="text">Re: dcg question from Learn Prolog Now</title>
  <summary type="html" xml:space="preserve">
  no, the file loaded fine &lt;br&gt; done. &lt;br&gt; well, for some reason, when I hit &amp;quot;;&amp;quot; to see the next solution, I get &lt;br&gt; the same answer repeated 4 more times : &lt;br&gt; ?- s(X,[]), member(and, X). &lt;br&gt; X = [the, woman, shoots, the, woman, and, the, woman, shoots|...] ; &lt;br&gt; X = [the, woman, shoots, the, woman, and, the, woman, shoots|...] ;
  </summary>
  </entry>
  <entry>
  <author>
  <name>fsaenzperez</name>
  <email>fsaenzpe...@gmail.com</email>
  </author>
  <updated>2010-03-17T12:22:11Z</updated>
  <id>http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/5857d8195986daf5/62d9187ef7761f1a?show_docid=62d9187ef7761f1a</id>
  <link href="http://groups.google.at/group/comp.lang.prolog/browse_thread/thread/5857d8195986daf5/62d9187ef7761f1a?show_docid=62d9187ef7761f1a"/>
  <title type="text">DES 1.8.1 Released</title>
  <summary type="html" xml:space="preserve">
  [Apologies for multiple receptions] &lt;br&gt; Hello. &lt;br&gt; In order to cellebrate the resurgence of Datalog in academia and &lt;br&gt; industry (Datalog 2.0 workhop, just running now), I would like &lt;br&gt; to contribute with a modest new release of DES fixing some problems. &lt;br&gt; So, the new release &lt;br&gt; Datalog Educational System version 1.8.1
  </summary>
  </entry>
</feed>
