Hi,
I have managed to build interpsys with dlopen in the image.
Next step is to use dlopen, which in fact is the more interesting part.
Has anybody experience with dlopen yet?
Regards
Gernot
hawkings# /home/hueber/src/axiom--main--1--patch-49/obj/freebsd/bin/interpsys
GCL (GNU Common Lisp) 2.
C Y <[EMAIL PROTECTED]> writes:
[...]
| I prefer the idea of "one file per concept",
strongly agreed.
For me, the issue here is that of organizing information for human
comprehension. I simply cannot handle gigantic file, no matter how
powerful my computers are.
-- Gaby
_
--- Ralf Hemmecke <[EMAIL PROTECTED]> wrote:
> But what I think is important is, not just to write HUGE files that
> nobody can manage anymore, but to add a bit of structure to it.
> Nowadays we could write a whole book into just one latex file. But
> I bet, most people structure that via severa
On Thursday, August 03, 2006 2:34 PM Ralf Hemmecke wrote:
> ...
> And the "book" idea is good, but it is not perfect. You have
> already said that you want to write books for different people,
> look from a different perspective onto the same data. So wouldn't
> it be nice to have all these data
On 08/03/2006 04:10 PM, root wrote:
I guess the literate idea even says that it does not matter how a file
is called. It is most important that you write a paper from which you
can generate all the code (even different files from one pamphlet
source). That sounds nice, but in some sense I find
Bob,
Thanks very much for the reference to this new work. Having
actually written a tensor package for Maple a few years ago
and now contemplating the limitations of the CartesianTensor
domain in Axiom, I do have a great respect for this problem.
On Thursday, August 03, 2006 12:58 PM you wrote:
>
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| This email is just to say "thanks" again
Thank *you*.
Indeed, this is excellent!
-- Gaby
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-d
Today appeared "A field-theory motivated approach to symbolic computer
algebra":http://arxiv.org/abs/cs.SC/0608005 which is of course very
interesting to me. Anyone who has used any tensor package in any CAS
will sympathize with the goals of the author.
The code is GPL and he even wrote a texmac
Gaby, Ralf, Cliff, Antoine, Alfredo, and others who I hope
I haven't forgotten:
Thank you all very much for the valuable comments, criticisms
and suggestions regarding the Axiom Wiki web site that you have
contributed to this thread. I have read each message carefully
although I have not responded
Hi,
Here is the patchfile. Pls check.
util.ht is broken, but I think this is not a FreeBSD issue. I used one
from an older build and hyperdoc works again.
You need bash, gsed and gawk installed!
Install gcl from the ports with "--enable-ansi" removed from the
Makefile.
Go into bash, start ./conf
I have not been successful building Axiom on FreeBSD.
I would like to see your patches.
Tim
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
Hi,
I am working with Axiom/Aldor on FreeBSD systems (FreeBSD 6.1 and 5.4,
gcl-2.6.6 and gcl-2.6.7). After Axiom compiles fine (with some with some
minor patches I will provide after cleaning up them). Especially the
Aldor part causes some serious headache.
Is anybody interested in or able to bui
> I guess the literate idea even says that it does not matter how a file
> is called. It is most important that you write a paper from which you
> can generate all the code (even different files from one pamphlet
> source). That sounds nice, but in some sense I find that very difficult
> to mai
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| Hi Gaby,
|
| > | If for the bootstrapping file configure.ac.pamplet (that should be
| > | enough?) we restrict to just several code chunks of the form
| > | | <<*>>=
| > | code here
| > | @
| > | ...
| > | <<*>>=
| > | other code
| > | @
| > | | All the
Makefile.am does not need to be linear. In fact, Makefile.am is
sufficiently high-level enough that if and when we get there, we will
see that Tim already did the job. We just need to re-structure
Makefile.pamphlet first. You won't have to write Makefile.am,
because you will write Makefile.pamp
Hi Gaby,
| If for the bootstrapping file configure.ac.pamplet (that should be
| enough?) we restrict to just several code chunks of the form
|
| <<*>>=
| code here
| @
| ...
| <<*>>=
| other code
| @
|
| All these <<*>> chunks are linearly concatenated by notangle to give
| the final output.
Hi Bill,
thank you for all your changes.
I just want to say that I like the *red* "Be Bold!" link in the "Add
Comments" section at the end of each page. I like it even if I think
that commenting on the page is not too helpful. People should really
edit the page if they don't like something th
17 matches
Mail list logo
