This post originated from an RSS feed registered with Python Buzz
by Ng Pheng Siong.
Original Post: Prolog
Feed Title: (render-blog Ng Pheng Siong)
Feed URL: http://sandbox.rulemaker.net/ngps/rdf10_xml
Feed Description: Just another this here thing blog.
So why does one program in an embedded Prolog, as compared to doing so
in "pure" Prolog? For starters, there's the "it looks
alien" thing: if Common Lisp or Smalltalk are strange to the
"average hacker" steeped in Algol-family languages, Prolog will
require even more rewiring of the mind. Programming Prolog embedded
in a host language allows the programmer to use Prolog for what it is
good at, without him attempting to also write a GUI or serve content over
HTTP in Prolog.
A capable host language like Common Lisp can implement Prolog in
itself and provide seamless bidirectional interfacing, make Prolog facts and rules persistent in "native" format, operate on the tuples in an SQL database directly as if they are Prolog facts without a whole lot
of extra infrastructure, compile to native code, etc.