Pike  v8.0.1116
About: Pike is an interpreted, high-level, cross-platform, dynamic programming language (syntax similar to Java and C).
  Fossies Dox: Pike-v8.0.1116.tar.gz  ("unofficial" and yet experimental doxygen-generated source code documentation)  

Pike Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies Pike-v8.0.1116.tar.gz contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).
Pike by Fredrik Hübinette 1994-2001 and the Pike team 2001-2020

Permission to copy, modify, and distribute this source for any legal
purpose granted as long as my name is still attached to it.  More
specifically, the GPL, LGPL and MPL licenses apply to this software.

New releases can be found on http://pike.lysator.liu.se/download/
Report bugs at http://bugs.roxen.com/
There is also a mailing list, to subscribe to it mail:


If you are building Pike from git, read README-GIT instead.

The top-level makefile (in this directory, not the src directory) has
all the magic you need to build Pike. Just type 'make'.
To install type "make install" or "make install_interactive".

You will need a C compiler and libgmp. You probably also want to have
GNU make and libnettle.

If that doesn't work, refer to README-GIT, in particular the sections
on "MANUAL BUILDING" and, if needed, the section "IF IT DOESN'T WORK".


If you find a bug in the interpreter, the first thing to do is to make
sure the interpreter is compiled with PIKE_DEBUG defined.  If not,
recompile with PIKE_DEBUG and see if you get another error.  When
you've done this, please report the bug to us at
http://bugs.roxen.com/ and include as much as you can muster of the

  o The version of the driver. (Try pike --version or look in
  o What kind of system hardware/software you use (OS, compiler, etc.)
  o The piece of code that crashes or bugs, preferably in a very
    small Pike-script with the bug isolated.  Please send a complete
    running example of something that makes the interpreter bug.
  o A description of what it is that bugs and when.
  o If you know how, then also give us a backtrace and dump of vital
    variables at the point of crash.
  o Or, if you found the error and corrected it, just send us the
    bugfix along with a description of what you did and why.