SICStus Prolog IDE (SPIDER)

   \|//
   :-
   /|\\

• Installation.

  See the instructions on how to download and install SPIDER.

• Once you have installed SPIDER, you can proceed to create your first Prolog project with SPIDER.

  SPIDER Getting Started describes how to create a simple Prolog project as well as how to use some of the SPIDER features.

• Information for SPIDER Beta Testers contains information about the kind of feedback we need from our beta testers.
• Tips and Tricks contains information about how to best use SPIDER.
• Known issues contains information about various issues in the current beta release.
• Release History contains information about releases.

Features

Information about missing and future features is available in the Information for SPIDER Beta Testers.

• Semantic Highlighting

  Code is highlighted based on semantic properties such as singleton variables, definining occurrence …

• On-the-fly warnings

  The editor flags things like calls to undefined predicates, unreachable predicates, incorrect use of predicates and directives, missing declarations … Some warnings comes with quick-fixes, i.e. automatic source-code modifications that fixes the warned about issue.

  Problem markers are enabled also for Prolog code that is not open in an editor.

• Pop-up documentation

  Predicate documentation is parsed on-the-fly and shown when the mouse is hovering over a call. This works for both built-in and user-defined predicates.

  Related information, like mode/1 and block/1 directives and various inferred information (determinacy, output arguments) are also shown.

• Open Definition

  Clicking on a called predicate can bring up its source code.

  It is also possible to manually enter the name of any predicate, with completion, and go to its source code.

• Call Hierarchy

  Clicking on a predicate can bring up a tree of its callers and other references.

  

  A light weight version of this command that just opens the closest caller of the current predicate, is also available.

• Determinacy Analyzer

  Predicates are analyzed, on-the-fly, for potential non-determinacy or non-termination.

• Mode Analyzer

  Predicates are analyzed, on-the-fly, and likely output arguments are shown when hovering over the predicate in a goal.

• Document outline

  The predicates in a file are shown in an outline. They can be alphabetically sorted and non-exported predicates can be hidden from the outline.

• Predicates can be accurately renamed in an entire project. Variables can be renamed within a clause or directive.
• The number and order of arguments of a predicate can be changed, and all referencing code will be updated in an entire project.

  

  

  
  (As can be seen, SPIDER will warn about the fact that the newly introduced arguments must be given appropriate values.)

• Predicates can be created from selected code, and the code replaced with a call to the new predicate (“Extract Predicate”). A call to a predicate can be inlined, i.e. replaced with the corresponding clause body.
• Variables can introduced from a selected term; variables can be inlined, i.e. replaced with their value.
• Variable Bindings in Debugger

  The debugger shows the names and values of variables.

• Debugger Backtrace

  Backtrace is shown and there are buttons for common debugger actions (Step Over, Step Out, Redo, …).

• Source Code Debugging

  Source-linked debugging. Works also for code, like the SICStus library, that has no recorded source info.

• Breakpoints and Spy points

  Line Breakpoints and Spy points can be added by clicking in the left margin of editor.

• Prolog Toplevel

  The ordinary toplevel is still available, with input history and completion. This includes the traditional debugger interface.

  You can have multiple SICStus processes running, each in its own toplevel view.

• The Profile view shows profile information for code run with profiling enabled.
• The Coverage view view and editor margin annotation shows source code coverage information for code run with profiling enabled. This features requires SICStus 4.2 or later.
• Integrated SICStus Manual and other documentation.
• Works With Existing Code

  No need to reorganize your code, SPIDER can work with your existing folder structure.

• Powered by Eclipse

  Eclipse provides many features for free, like support for other programming languages, revision control, and much more.