Files needed to natively compile PARI 2.3.0 with MSVC6 and using it from Maple or Excel
Thanks to Karim Belabas for supporting to find out how the concurrent version 2.3.0 can be compiled using MSVC6!
To do it one needs additional files with which he supplied me. The result is a command line version with a somewhat
restricted comfort and missing assembler routines. But it works. The second section gives a DLL version, which can
be used from Maple. In both cases the complete MSVC projects can be downloaded.  The third sections provides a
solution how to use Pari from Excel (through VBA). (50 kB) are the files mp.c and pariinl.h to replace the distributed ones.

Please note: as licence the GNU GPL applies of course. You find Pari's homepage at

A raw command line version:

README.MSVC.AVt.txt (5 kB)
    A sketch how to proceed. (1150 kB)
    The complete MSVC project including needed files (see the readme). (990 kB)
    The compiled exe file.

DLL version to be called from Maple:

readme_pari_maple.txt (10 kB)
    A docu how to proceed. (1070 kB)
    The complete MSVC project including all needed files. (1114 kB)
    The compiled DLL file. (5 kB),  example_pari_mpl.mws.pdf (14 kB)
    An example Maple worksheet showing use of the stuff, printed in pdf format to look at without Maple..

DLL version to be called from Excel:

readme_pari_excel.txt (4 kB)
    A short docu. (2 kB)
    Sources (pari_xl.c and pari_xl.def) needed to compile. (978 kB)
    The compiled DLL file. (15 kB)
    An example Excel workbook showing how to use of the stuff.


 go up

feedback is welcome & if you want to drop me any comment ... mail-nospam

This software is provided "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.