• Swi Prolog Tutorial
• Swi Prolog For Mac Os X 10 11

The following Comparison of Prolog implementations provides a reference for the relative feature sets and performance of different implementations of the Prolog computer programming language.

Portability[edit]

There are Prolog implementations that are radically different, with different syntax and different semantics (e.g. Visual Prolog)^[1] and sub-communities have developed around different implementations.^[1]

Code that strictly conforms to the ISO-Prolog core language is portable across ISO-compliant implementations. However, the ISO standard for modules was never accepted by most Prolog implementors.^[1]

Canon PIXMA Drivers. Canon i-SENSYS Drivers. Canon ImageClass Drivers. Canon ImageRUNNER Drivers. We fully recommend you to either consult your physical user manual or seek additional information about your printer model on the official Canon website that features comprehensive software, manuals, drivers or firmware support.Supported Models, click for a full list.

Factors that can adversely affect portability include: use of bounded vs. unbounded integer arithmetic, additional types such as string objects, advanced numeric types (rationals, complex), feature extensions such as Unicode, threads, and tabling.^[2] Use of libraries unavailable in other implementations and library organisation:^[1]

Currently, the way predicates are spread over the libraries and system built-ins differs enormously. [..] Fortunately, there are only few cases where we find predicates with the same name but different semantics (e.g. delete/3)

Did I install something incorrectly? I'm running on a Mac OS X 10.9.1 Mavericks. I placed the SWI-Prolog application into my application folder and I also downloaded XQuartz per recommendation by the website. There are three sensible ways of installing SWI-Prolog on MacOS X, in increasing order of complexity:. Download the SWI-Prolog.

Main features[edit]

Operating system and Web-related features[edit]

Static analysis[edit]

Optimizations[edit]

Release[edit]

Benchmarks[edit]

• Benchmarking issues: Odd Prolog benchmarking, Performance differences.^[4]
• Benchmarking software: older, Dobry^{[permanent dead link]}, Aquarius benchmark suite, (Bothe, 1990),^[5](Demoen et al. 2001), benchmark descriptions
• Benchmarking results: B-Prolog, SICStus, XSB,^[6] SICStus vs Yap vs hProlog^[7]
• Benchmarking results: Survey of java prolog engines by Michael Zeising
• Benchmarking results: OpenRuleBench yearly open-source benchmark of rule engines

References[edit]

1. ^ ^abcdWielemaker, J.; Costa, V. T. S. (2011). 'On the Portability of Prolog Applications'. Practical Aspects of Declarative Languages. Lecture Notes in Computer Science. 6539. p. 69. CiteSeerX10.1.1.1030.9396. doi:10.1007/978-3-642-18378-2_8. ISBN978-3-642-18377-5.
2. ^Jan Wielemaker and Vıtor Santos Costa: Portability of Prolog programs: theory and case-studies. CICLOPS-WLPE Workshop 2010.
3. ^ ^abC/Java interface can also be used for graphics and OS control.
4. ^B. Demoen, and P. Nguyen, About unnecessary performance differences between Prolog implementations, Proceedings of the Colloquium on Implementation of Constraint and Logic Programming Systems (CICLOPS 2001)
5. ^Bothe, K. (1990). 'A prolog space benchmark suite'. ACM SIGPLAN Notices. 25 (12): 54–60. doi:10.1145/122193.122197.
6. ^A Summary of XSB Performance (1993)
7. ^Demoen, B.; Nguyen, P. L.; Vandeginste, R. (2002). 'Copying Garbage Collection for the WAM: to Mark or Not to Mark?'. Logic Programming. Lecture Notes in Computer Science. 2401. pp. 194–208. CiteSeerX10.1.1.13.2586. doi:10.1007/3-540-45619-8_14. ISBN978-3-540-43930-1.

External links[edit]

• Overview of Prolog Systems by Ulrich Neumerkel

Quickstart

1. Install Xcode and the Xcode Command Line Tools
2. Agree to Xcode license in Terminal: sudo xcodebuild -license
3. Install MacPorts for your version of the Mac operating system:

Installing MacPorts

MacPorts version 2.6.2 is available in various formats for download and installation (note, if you are upgrading to a new major release of macOS, see the migration info page):

• “pkg” installers for Catalina, Mojave, High Sierra and Sierra, for use with the macOS Installer. This is the simplest installation procedure that most users should follow after meeting the requirements listed below. Installers for legacy platforms El Capitan, Yosemite, Mavericks, Mountain Lion, Lion, Snow Leopard, Leopard and Tiger are also available.
• In source form as either a tar.bz2 package or a tar.gz one for manual compilation, if you intend to customize your installation in any way.
• Git clone of the unpackaged sources, if you wish to follow MacPorts development.
• The selfupdate target of the port(1) command, for users who already have MacPorts installed and wish to upgrade to a newer release.

Checksums for our packaged downloads are contained in the corresponding checksums file.

The public key to verify the detached GPG signatures can be found under the attachments section on jmr's wiki page. (Direct Link).

Please note that in order to install and run MacPorts on macOS, your system must have installations of the following components:

1. Apple's Xcode Developer Tools (version 11.0 or later for Catalina, 10.0 or later for Mojave, 9.0 or later for High Sierra, 8.0 or later for Sierra, 7.0 or later for El Capitan, 6.1 or later for Yosemite, 5.0.1 or later for Mavericks, 4.4 or later for Mountain Lion, 4.1 or later for Lion, 3.2 or later for Snow Leopard, or 3.1 or later for Leopard), found at the Apple Developer site, on your Mac operating system installation CDs/DVD, or in the Mac App Store. Using the latest available version that will run on your OS is highly recommended, except for Snow Leopard where the last free version, 3.2.6, is recommended.

2. Apple's Command Line Developer Tools can be installed on recent OS versions by running this command in the Terminal:

   Older versions are found at the Apple Developer site, or they can be installed from within Xcode back to version 4. Users of Xcode 3 or earlier can install them by ensuring that the appropriate option(s) are selected at the time of Xcode's install ('UNIX Development', 'System Tools', 'Command Line Tools', or 'Command Line Support').

3. Xcode 4 and later users need to first accept the Xcode EULA by either launching Xcode or running:
4. (Optional) The X11 windowing environment for ports that depend on the functionality it provides to run. You have multiple choices for an X11 server:
   • Install the xorg-server port from MacPorts (recommended).
   • The XQuartz Project provides a complete X11 release for macOS including server and client libraries and applications. It has however not been updated since 2016.
   • Apple's X11.app is provided by the “X11 User” package on older OS versions. It is always installed on Lion, and is an optional installation on your system CDs/DVD with previous OS versions.

macOS Package (.pkg) Installer

The easiest way to install MacPorts on a Mac is by downloading the pkg or dmg for Catalina, Mojave, High Sierra, Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion, Lion, Snow Leopard, Leopard or Tiger and running the system's Installer by double-clicking on the pkg contained therein, following the on-screen instructions until completion.

This procedure will place a fully-functional and default MacPorts installation on your host system, ready for usage. If needed your shell configuration files will be adapted by the installer to include the necessary settings to run MacPorts and the programs it installs, but you may need to open a new shell for these changes to take effect.

The MacPorts “selfupdate” command will also be run for you by the installer to ensure you have our latest available release and the latest revisions to the “Portfiles” that contain the instructions employed in the building and installation of ports. After installation is done, it is recommended that you run this step manually on a regular basis to to keep your MacPorts system always current:

At this point you should be ready to enjoy MacPorts!

Type “man port” at the command line prompt and/or browse over to our Guide to find out more information about using MacPorts. Help is also available.

Source Installation

If on the other hand you decide to install MacPorts from source, there are still a couple of things you will need to do after downloading the tarball before you can start installing ports, namely compiling and installing MacPorts itself:

1. “cd” into the directory where you downloaded the package and run “tar xjvf MacPorts-2.6.2.tar.bz2” or “tar xzvf MacPorts-2.6.2.tar.gz”, depending on whether you downloaded the bz2 tarball or the gz one, respectively.
2. Build and install the recently unpacked sources:
   • cd MacPorts-2.6.2
   • ./configure && make && sudo make install
   Optionally:
   • cd ./
   • rm -rf MacPorts-2.6.2*

These steps need to be perfomed from an administrator account, for which “sudo” will ask the password upon installation. This procedure will install a pristine MacPorts system and, if the optional steps are taken, remove the as of now unnecessary MacPorts-2.6.2 source directory and corresponding tarball.

To customize your installation you should read the output of “./configure --help more” and pass the appropriate options for the settings you wish to tweak to the configuration script in the steps detailed above.

You will need to manually adapt your shell's environment to work with MacPorts and your chosen installation prefix (the value passed to configure's --prefix flag, defaulting to /opt/local):

• Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH environment variable so that MacPorts-installed programs take precedence over system-provided programs of the same name.
• If a standard MANPATH environment variable already exists (that is, one that doesn't contain any empty components), add the ${prefix}/share/man path to it so that MacPorts-installed man pages are found by your shell.
• For Tiger and earlier only, add an appropriate X11 DISPLAY environment variable to run X11-dependent programs, as Leopard takes care of this requirement on its own.

Lastly, you need to synchronize your installation with the MacPorts rsync server:

Upon completion MacPorts will be ready to install ports!

It is recommended to run the above command on a regular basis to keep your installation current. Type “man port” at the command line prompt and/or browse over to our Guide to find out more information about using MacPorts. Help is also available.

Git Sources

If you are developer or a user with a taste for the bleeding edge and wish for the latest changes and feature additions, you may acquire the MacPorts sources through git. See the Guide section on installing from git.

Purpose-specific branches are also available at the https://github.com/macports/macports-base/branches url.

Alternatively, if you'd simply like to view the git repository without checking it out, you can do so via the GitHub web interface.

Selfupdate

If you already have MacPorts installed and have no restrictions to use the rsync networking protocol (tcp port 873 by default), the easiest way to upgrade to our latest available release, 2.6.2, is by using the selfupdate target of the port(1) command. This will both update your ports tree (by performing a sync operation) and rebuild your current installation if it's outdated, preserving your customizations, if any.

Other Platforms

Running on platforms other than macOS is not the main focus of The MacPorts Project, so remaining cross-platform is not an actively-pursued development goal. Nevertheless, it is not an actively-discouraged goal either and as a result some experimental support does exist for other POSIX-compliant platforms such as *BSD and GNU/Linux.

The full list of requirements to run MacPorts on these other platforms is as follows (we assume you have the basics such as GCC and X11):

• Tcl (8.4 or 8.5), with threads.
• mtree for directory hierarchy.
• rsync for syncing the ports.
• cURL for downloading distfiles.
• SQLite for the port registry.
• GNUstep (Base), for Foundation (optional, can be disabled via configure args).
• OpenSSL for signature verification, and optionally for checksums. libmd may be used instead for checksums.

Normally you must install from source or from an git checkout to run MacPorts on any of these platforms.

Swi Prolog Tutorial

Help

Help on a wide variety of topics is also available in the project Guide and through our Trac portal should you run into any problems installing and/or using MacPorts. Of particular relevance are the installation & usage sections of the former and the FAQ section of the Wiki, where we keep track of questions frequently fielded on our mailing lists.

Swi Prolog For Mac Os X 10 11

If any of these resources do not answer your questions or if you need any kind of extended support, there are many ways to contact us!