Changes http://wiki.axiom-developer.org/FAQ/diff --
++added: +1. **What is Axiom's license?** + + Axiom is free software, available under a BSD like license. For more details, please have a look in the + <a href="http://savannah.nongnu.org/cgi-bin/viewcvs/axiom/axiom/license/";>licences available in the CVS repository</a>. + + 1. **How can I contribute code to Axiom?** ++added: + +1. **What is the future of Axiom?** + + Tim Daly is Lead Axiom Developer. He has a fairly + <a href="http://axiom.axiom-developer.org/axiom-website/currentstate.html";>detailed agenda</a> + for Axiom. + + +1. **What is the size of Axiom?** + Axiom is: ((--rhx: this data should be generated automatically)) + + * 92 MB of source code + + * about 56 MB once compiled + + * 403591 lines for the interpreted in 220 files + + * 255790 lines of algebra in 371 files + + +1. **On which system is known to run Axiom?** + + People have compiled and run Axiom on: + + * Debian GNU/Linux 3.0, on i386, Sparc64. + On PowerPC architecture, Axiom will not build because it requires gcc-3.3 + (which supports -mlong-calls option, supporting relocs of more tha 24 bits). + + * Debian GNU/Linux sid, on mipsel, ia64, i386, ppc, alpha, and sparc (and more to come!) + + * RedHat Linux 7.3 and 9.0 on i386 + + * Slackware Linux 8.0.01 on Intel ProLiant ML530 [EMAIL PROTECTED] + + * Red Hat Linux 8.0 on Intel ProLiant ML530 [EMAIL PROTECTED] -- Red Hat Enterprise Linux ES release 2.1 (Panama) + + * SuSE Linux Ent Svr 8.0 on Intel ProLiant DL360 G2 [EMAIL PROTECTED] + + * Red Flag Linux 4.0 + + * Microsoft Windows + + 1. **Where can I find articles related to Axiom and Aldor?** ??changed: - Look at http://portal.axiom-developer.org/refs/articles/. + Look at <a href="http://portal.axiom-developer.org/refs/articles/";>http://portal.axiom-developer.org/refs/articles/</a>. + ++added: + 1. **How to create new pages on AxiomWiki?** ++added: + +1. **How can I download Axiom?** + + Look at AxiomDownload. + + 1. **I have found a bug. What should I do?** ++added: + +1. **How can I submit a patch?** + + In general a patch file is of the form:: + + cd the.dir + diff -Naur file.pamphlet file.pamphlet.new >the.dir.file.pamphlet.patch + + Send the patch to <a href="mailto:[EMAIL PROTECTED]">Tim Daly</a>. + + This has several features: + + * it tells where the patch is being applied + + * the Naur options gives context + + * the impact of a change to multiple files become visible + + Tim Daly reads the patches before applying them, so be sure to document the + reasons for the change in the pamphlet file. It may seem trivial + but remember that I didn't do the initial analysis so he, and others, + will have to understand after the fact. + + In most cases in a pamphlet file if you're changing a few lines + of code or a whole function it should be documented thus:: + + ... + (defun foo () + (list + "this is ok code" + "this is broken code" + "this is also broken" + "this is ok" + ) + ) + + turns into:: + + \subsection{foo list fix} + This code used to read: + \begin{verbatim} + "this is broken code" + "this is also broken" + \end{verbatim} + but clearly the elements of the list are wrong. We are going to + print this list for the user so we don't want them to know anything + is broken. Thus we have wonderful new code that will inspire confidence. + This list is printed with the [[printlist]] function. + <<foo list fix>>= + "this is great code" + "this inspires confidence" + @ + ... + (defun foo () + (list + "this is ok code" + <<foo list fix>> + "this is ok" + ) + ) + + and, yes, that this is tedious. + + In general, it is also useful to update the pamphlet files with + documentation-only changes as you understand what a block of code + is intended to do. Most of this information has been lost to history + and the world can leverage your efforts at understanding if you take + the time to document it. In many ways this is as important as fixing + the code. + + + **PS**: We will soon have another way to submit patches, since any modification should + first go into the <a href="../AxiomDownload">silver branch</a> and survive public review, + but the need to document properly will not be modified. + + 1. **How should pamphlet files look like?** -- forwarded from http://wiki.axiom-developer.org/[EMAIL PROTECTED]
