1 Sep 03:33 2002

### Re: status of "affine" package?

David and Michele Holmgren <holmgrenm <at> shaw.ca> writes:

>  Does anyone have any information regarding the status of the
> "affine" package for Maxima?  Has it been updated at all from the
> version available at the old Maxima site?  I took a stab at
> compiling this recently, but failed miserably :)  If nothing has
> been done, I might try some work on it...

Actually, I have made a bunch of changes and added a demo file (which
shows how to compute, though somewhat awkwardly, a standard
non-trivial example of a free resolution).  Some time after 5.9.0, if
nobody objects, I will check in Schelter's original sources and
broken.

Meanwhile, if you are interested, please take a look at

http://members.inode.at/wjenkner/maxima/my-affine.tar.gz

I added an affine.system' file, so I suggest the following steps:
Unpack this somewhere, cd in affine', start maxima, then type

to_lisp();

(mk:compile-system "affine")

Then exit and restart maxima, type

to_lisp();



1 Sep 04:11 2002

### Re: status of "affine" package?

Hi Wolfgang,

OK, thanks!  I'll try this out once I get the latest Maxima compiled, etc..
I had a feeling that someone might be working on "affine".

Dave Holmgren

----- Original Message -----
From: "Wolfgang Jenkner" <wjenkner <at> inode.at>
To: "David and Michele Holmgren" <holmgrenm <at> shaw.ca>
Cc: "Maxima List" <maxima <at> www.ma.utexas.edu>
Sent: Saturday, August 31, 2002 7:33 PM
Subject: Re: [Maxima] status of "affine" package?

David and Michele Holmgren <holmgrenm <at> shaw.ca> writes:

> Does anyone have any information regarding the status of the
> "affine" package for Maxima? Has it been updated at all from the
> version available at the old Maxima site? I took a stab at
> compiling this recently, but failed miserably :) If nothing has
> been done, I might try some work on it...

Actually, I have made a bunch of changes and added a demo file (which
shows how to compute, though somewhat awkwardly, a standard
non-trivial example of a free resolution).  Some time after 5.9.0, if
nobody objects, I will check in Schelter's original sources and
broken.

Meanwhile, if you are interested, please take a look at


1 Sep 14:53 2002

### Re: Re: LambdaTensor and Maxima


Thomas Fischbacher <Thomas.Fischbacher <at> Physik.Uni-Muenchen.DE> writes:

> Here my diff:
>
> 126c126
> <           (COND ((NULL (SETQ IL (INTERSECTION L1 L2)))
> ---
> >           (COND ((NULL (SETQ IL (MAXIMA-HYP-INTERSECTION L1 L2)))
> 471c471

[...]

Thanks for the fix.  I changed the CVS source accordingly.

In general such symbols are shadowed (see maxima-package.lisp).
However INTERSECTION is used only in hyp.lisp, so just renaming it
makes more sense, I guess.

> I would strongly suggest letting a primitive code-walker analyze the
> source for other such conflicts.

Actually, e.g. Clisp gives a continuable error or warning in such
cases (for locked packages).  Judging from this, there seems to be no
other conflict with the COMMON-LISP package.

Wolfgang
--

--
wjenkner <at> inode.at


1 Sep 17:36 2002

### Re: 5.9.0 release candidate 1

James Amundson пишет:
> I have updated a tarball for 5.9.0 release candidate 1 to the
> sourceforge site. Please find all show-stopping problems soon so that we
> can release next week. I know there are a few fixes available that have
> not made it into the release -- it's always going to be that way. (I
> have to keep telling myself that.)
>
> I would like to hear reports from as many platforms as possible. Windows
> is of particular interest because it is so different from the unix-like
> platforms.
>
> --Jim
> _______________________________________________
> Maxima mailing list
> Maxima <at> www.math.utexas.edu
> http://www.math.utexas.edu/mailman/listinfo/maxima
>
>
>

I've noticed that /interfaces/emacs/emaxima/emaxima.lisp
is missing in the RC1 tarball.

--

--

<vvzhy <at> mail.ru>
<vvzhy <at> netorn.ru>
<vvzhy <at> yandex.ru>
<vvzhy <at> td.lpi.ac.ru>


2 Sep 10:23 2002

### Re: 5.9.0 release candidate 1

Hi Stephen.

PROBLEM 1 - gcl path

> sh-2.04$gcl > /e/usr/local/bin/gcl: e:/Gnu/e:/usr/local/lib/gcl-2.5.0/unixport/saved_gcl.exe: No such file or directory > /e/usr/local/bin/gcl: exec: e:/Gnu/e:/usr/local/lib/gcl-2.5.0/unixport/saved_gcl.exe: cannot execute: No such file or directory > > for some reason, sh is prepending the current directory in the call to > exec. To fix this, just edit the path to "saved_gcl.exe" (JUST the path, NOT the arguments) in the gcl script so that it uses MSYS format rather than native Windows eg: ====================================== #!/bin/sh exec /g/gclm/lib/gcl-2.5.0/unixport/saved_gcl.exe \ -dir g:/gclm/lib/gcl-2.5.0/unixport/ \ -libdir g:/gclm/lib/gcl-2.5.0/ \ -eval '(setq si::*allow-gzipped-file* t)' \ "$ <at> "

======================================



2 Sep 22:02 2002

### maxima and inequalities

Hello

Is it planned to add solving inequalities for the future release of
maxima ?
--

--
****************************
Michel Gosse
michel.gosse <at> ac-poitiers.fr
michel.gosse <at> freesbee.fr
****************************

3 Sep 03:10 2002

### RE: [Gcl-devel] Re: 5.9.0 release candidate 1

I managed to build a working maxima with gcl/mingw/msys last night,
using current CVS of both.  Testsuite results were OK.

I found and resolved Problem 1, and stumbled over a couple of other
minor gnits.  I will work through it again and refine my notes.
Also tried using gcc-3.2, but the raw_gcl.exe choked.  I may
investigate further.

David

-----Original Message-----
From: Mike Thomas [mailto:miketh <at> brisbane.paradigmgeo.com]
Sent: Monday, 2 September 2002 6:24
To: Stephen Leake
Cc: gcl-devel <at> gnu.org; Maxima List
Subject: [Gcl-devel] Re: [Maxima] 5.9.0 release candidate 1

Hi Stephen.

PROBLEM 1 - gcl path

> sh-2.04\$ gcl
> /e/usr/local/bin/gcl:
e:/Gnu/e:/usr/local/lib/gcl-2.5.0/unixport/saved_gcl.exe: No such file or
directory
> /e/usr/local/bin/gcl: exec:
e:/Gnu/e:/usr/local/lib/gcl-2.5.0/unixport/saved_gcl.exe: cannot execute: No
such file or directory
>
> for some reason, sh is prepending the current directory in the call to


3 Sep 04:21 2002

### Re: maxima and inequalities

Can you define what you mean by solving inequalities and
what algorithms you would expect?

For example, given the range of possible expressions
in maxima,  the predicate  "f(x)>0" is undecidable.
On the other hand, is(3<4)   is probably already solved.

Real inequalities? integer inequalities?

I don't know if anyone has plans to do better, but
it is certainly possible to add such features to
maxima.  If you volunteer to do so, I think people

is (abs(sin(x))<=1)  for example?  The commercial macsyma says true.

RJF

Gosse Michel wrote:

> Hello
>
> Is it planned to add solving inequalities for the future release of
> maxima ?
>

3 Sep 04:22 2002

### Re: maxima and inequalities

oops ... is (abs(sin(x)<=1) is true.

Gosse Michel wrote:

> Hello
>
> Is it planned to add solving inequalities for the future release of
> maxima ?
>

3 Sep 05:40 2002

### Re: [Gcl-devel] Re: 5.9.0 release very close

Greetings, and thanks for looking into this.

I have a solution, which is not particularly pretty, but which I can
submit in the form of a patch to src/Makefile.am after testing here
for a couple of days.  So if you can wait a bit, it would be
appreciated.  If not, I can apply the patch to the Debian package, and
we can shoot for the next release.

This whole issue has brought up a couple of ideas, which may prove
important to future gcl development.

1) Dr. Shelter chose to link the maxima objects into gcl via ld
instead of (load ...), even when this would have been possible on
i386 and sparc.  Perhaps this was just to make the build as general
as possible.  But perhaps it makes a significant difference to
gcl/maxima performance, as all those objects are out of the lisp
core and linked into the static .text section of the executable.
Hopefully I'll have some numbers on this soon.

2) Such a link operation could be straightforwardly aranged to occur
"filename")(init-image "filename" "saved_filename")(by), since a C
compiler and its linker are guaranteed to be available where gcl
is.  This would eliminate the biggest objection to the old build
system IMHO, which was the necessity of having a gcl build
directory around when building maxima.

3) The right way to do this is to ship the bulk of gcl in a shared
library, -lgcl.  Should save *a lot* of space in a multi-user
environment too.  I've tried this, and there is some strange