pari  2.15.0
About: PARI/GP is a computer algebra system designed for fast computations in number theory (factorizations, algebraic number theory, elliptic curves...), but also contains a large number of other mathematical functions.
  Fossies Dox: pari-2.15.0.tar.gz  ("unofficial" and yet experimental doxygen-generated source code documentation)  

No Matches
pari 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 pari-2.15.0.tar.gz contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).
This is PARI/GP, version 2.15.x (*).

PARI/GP Number Theory-oriented Computer Algebra System
        Copyright (C) 2000-2022 The PARI Group, Bordeaux.


To get started, run

  cd doc; tex INSTALL.tex

and have a look at the file INSTALL.dvi, extracted verbatim from Appendix A
of the User Manual. (Or pdftex INSTALL.tex if PDF files are more convenient.)
If you are in a hurry, look at the ASCII file 'INSTALL' but a lot of
information is missing there.

Once 'Configure' has been run, 'make doc' typesets separate user's manual for
GP and libpari, a tutorial and reference card in directory doc.

The file NEW contains new features with respect to previous stable versions.
The file COMPAT warns about incompatible changes. See the files
CHANGES* for a terse description of successive patches.

For the adventurous: to check out bleeding-edge development versions of
PARI/GP, see the file README-git.

Afterwards, you're on your own.


There are three mailing lists devoted to the PARI/GP package, and most
feedback should be directed to those. They are:

* pari-announce: to announce major version changes. You can't write to this
one, but you should probably subscribe.

* pari-dev: for everything related to the development of PARI, including
suggestions, technical questions, bug reports or patch submissions.

* pari-users: for everything else.

To subscribe, send empty messages respectively to

with a Subject: containing the word "subscribe".

If you are not a member of any of those lists and do not want to become
one, you can write to us at

We may forward your mail to the lists above and will definitely try to
correct faulty behaviour, if necessary. But we cannot promise that you
will get an individual answer.

Last but not least, PARI home page can be found at

  Thanks for your support, and have fun !


PARI/GP is free software; you can redistribute it and/or modify it under the
terms of the GNU General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option) any later
version. It is distributed in the hope that it will be useful, but WITHOUT

Check the License for details. You should have received a copy of it, along
with the package; see the file 'COPYING'. If not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

(*) Version numbers have the shape: MAJOR.MINOR.patchlevel.status. The status
increases through {alpha, beta, release}. New features are introduced during
the `alpha' phase, tested during `beta', and declared stable when `release'
is reached.
The MAJOR version number will not change for a while.
The MINOR version number increases by 2 when a new status cycle starts (as
soon as a 'release' version is out): odd numbers are reserved for 'released'
versions, even ones for alpha/beta phase.
The patchlevel goes up each time we feel an upgrade is necessary (improvement
or bugfix). 'Release' versions may be updated with further patchlevels if
important bugs need to be fixed before the next cycle reaches completion.