Re: [fricas-devel] FriCAS status

Since I will most probably have no further time till Monday, I prepared the install.rst and download.rst now. You can find it in my github repo in branch wip/rst. https://github.com/hemmecke/fricas/tree/wip/rst/src/doc/sphinx/source The rendered pages are at

Re: [fricas-devel] FriCAS status

So... download.rst and install.rst and order minor docfixes have to be done. Are you working on this? Yes. I already have nearly everything, but need to clean up and reread. I will put something to my repo soon. Unfortunately, I am on travel and family affairs interrupt me quite a bit.

Re: [fricas-devel] FriCAS status

On Sat, Jul 1, 2023 at 7:55 PM Waldek Hebisch wrote: > > On Fri, Jun 30, 2023 at 03:03:27PM +0200, Ralf Hemmecke wrote: > > So... download.rst and install.rst and order minor docfixes have to be done. > > Are you working on this? Concerning download.rst, my idea of download > page was to put

Re: [fricas-devel] FriCAS status

On Fri, Jun 30, 2023 at 03:03:27PM +0200, Ralf Hemmecke wrote: > So... download.rst and install.rst and order minor docfixes have to be done. Are you working on this? Concerning download.rst, my idea of download page was to put there links to appropriate binaries. This is somewhat fragile info,

Re: [fricas-devel] FriCAS status and jFriCAS

On Fri, Jun 30, 2023 at 03:03:27PM +0200, Ralf Hemmecke wrote: > On 30.06.23 00:20, Ralf Hemmecke wrote: > > From my side I only see fixing of download.rst and install.rst > > (INSTALL) (ImageMagick) and removing the problem with a failing sphinx > > build of fricas.github.io. I'm afraid that I

Re: [fricas-devel] FriCAS status and jFriCAS

On 30.06.23 00:20, Ralf Hemmecke wrote: From my side I only see fixing of download.rst and install.rst (INSTALL) (ImageMagick) and removing the problem with a failing sphinx build of fricas.github.io. I'm afraid that I might not be able to do this tomorrow. Let's see how I can manage.

Re: [fricas-devel] FriCAS status and jFriCAS

On 25.06.23 19:58, Waldek Hebisch wrote: On Sun, Jun 25, 2023 at 04:13:46PM +0200, Ralf Hemmecke wrote: Similarly with mathprintWithNumber. But I guess mathPrintWithNumber is too late for the next release. Well, I was thinking about this. The attached patch should handle this. Just set

Re: [fricas-devel] FriCAS status and jFriCAS

On Tue, Jun 27, 2023 at 07:37:35PM +0200, Ralf Hemmecke wrote: > On 27.06.23 16:37, Waldek Hebisch wrote: > > > Actually, my question is whether it would be possible to clone a running > > > fricas session and continue with some computation in one clone with at the > > > same time with another

Re: [fricas-devel] FriCAS status and jFriCAS

On 27.06.23 16:37, Waldek Hebisch wrote: Actually, my question is whether it would be possible to clone a running fricas session and continue with some computation in one clone with at the same time with another computation in another clone? Well, that is what Unix fork is doing. OK, yes,

Re: [fricas-devel] FriCAS status and jFriCAS

On Tue, Jun 27, 2023 at 03:32:30PM +0200, Ralf Hemmecke wrote: > On 27.06.23 14:07, Waldek Hebisch wrote: > > > > Both Lisp version and the above behave rather badly when called > > > > from command line (the same is true for parseAndEvalStr). > > > > Namely, after calling it interpreter is

Re: [fricas-devel] FriCAS status and jFriCAS

On 27.06.23 14:07, Waldek Hebisch wrote: Both Lisp version and the above behave rather badly when called from command line (the same is true for parseAndEvalStr). Namely, after calling it interpreter is apparently waiting for more input from the string, but none is coming. So command line is

Re: [fricas-devel] FriCAS status and jFriCAS

On Tue, Jun 27, 2023 at 07:34:03AM +0200, Ralf Hemmecke wrote: > > AFACS in Boot this is: > > > > interpret_block(code) == > > $newcompErrorCount : local := 0 > > $inclAssertions : local := [] > > $ncMsgList : local := [] > > $erMsgToss : local := false > > $lastPos :

Re: [fricas-devel] FriCAS status and jFriCAS

AFACS in Boot this is: interpret_block(code) == $newcompErrorCount : local := 0 $inclAssertions : local := [] $ncMsgList : local := [] $erMsgToss : local := false $lastPos : local := $nopos $EchoLines : local := false st := MAKE_-STRING_-INPUT_-STREAM(code)

Re: [fricas-devel] FriCAS status and jFriCAS

On Mon, Jun 26, 2023 at 11:43:10PM +0200, Ralf Hemmecke wrote: > > > The definition of |interpret-block| would also be a nice addition to > > > FriCAS, > > > since it allows multi-line strings to be interpreted as if coming from a > > > file (with intendation working correctly). > > > > > >

Re: [fricas-devel] FriCAS status and jFriCAS

On 25.06.23 19:58, Waldek Hebisch wrote: On Sun, Jun 25, 2023 at 04:13:46PM +0200, Ralf Hemmecke wrote: https://github.com/fricas/jfricas/commit/78be121a4b10ee4183d4e097547c05a4756da633 OK I've opened https://github.com/fricas/fricas/pull/129 and will commit tomorrow night. Similarly

Re: [fricas-devel] FriCAS status

On Mon, Jun 26, 2023 at 7:20 AM 'Nasser M. Abbasi' via FriCAS - computer algebra system wrote: > > I setup new VBox with new Linux, and installed sagemath. > > There is an option with sage to ask it to install Fricas if you want > afterwords, and I used that option, it is > > sage -i fricas

Fwd: [fricas-devel] FriCAS status and jFriCAS

M. Abbasi' via FriCAS - computer algebra system Date: Mon, Jun 26, 2023 at 12:11 AM Subject: Re: [fricas-devel] FriCAS status and jFriCAS To: FriCAS - computer algebra system opps, very sorry. I had to re-run this Fricas small test again on sagemath 10. Please ignore the above post. Here

Re: [fricas-devel] FriCAS status

On 26.06.23 08:20, 'Nasser M. Abbasi' via FriCAS - computer algebra system wrote: sage -i fricas There is no difference in connection mechanism if one installs Fricas outside sage or let it install using the above command. Well, the sage people make it easy to install FriCAS via "sage -i

Re: [fricas-devel] FriCAS status

On 26.06.23 01:11, 'Nasser M. Abbasi' via FriCAS - computer algebra system wrote: Any way, I just rebuild sagemath again now from scratch and made sure now to not make it build Fricas 1.3.8 as I did before, and re-run the tests. I run a standard sage (with no particular options used when I

Re: [fricas-devel] FriCAS status and jFriCAS

opps, very sorry. I had to re-run this Fricas small test again on sagemath 10. Please ignore the above post. Here is the correct one: It turned out sagemath had its own internal fricas buildin, and I forgot about that and thought because I changed the PATH, sagemath will now use the new

Re: [fricas-devel] FriCAS status and jFriCAS

On Sun, Jun 25, 2023 at 04:13:46PM +0200, Ralf Hemmecke wrote: > > I am trying to use sbcl-1.4.6. ATM it seems that it works. > > However, since the process uses different, newer environment > > (Gentoo) there are possible glitches. I have now put test > > tarball at > > > >

[fricas-devel] FriCAS status and jFriCAS

I am trying to use sbcl-1.4.6. ATM it seems that it works. However, since the process uses different, newer environment (Gentoo) there are possible glitches. I have now put test tarball at http://www.math.uni.wroc.pl/~hebisch/fricas/fricas-1.3.9-pre.amd64.tar.bz2 binary works. In

Re: [fricas-devel] FriCAS status

On Sat, Jun 24, 2023 at 08:46:25PM -0700, 'Nasser M. Abbasi' via FriCAS - computer algebra system wrote: > FYI, > > I've done a quick initial Fricas integration test for > > >which fricas > /home/me/TMP/usr/local/bin/fricas > > >fricas --version > FriCAS 2023-06-17 > based on sbcl 1.4.16 > >

Re: [fricas-devel] FriCAS status

On 25.06.23 05:46, 'Nasser M. Abbasi' via FriCAS - computer algebra system wrote: FYI, I've done a quick initial Fricas integration test for ... This is the result. The good news is that there were no problems found and no regression. Thank you, Nasser. I think, it would be a good idea

Re: [fricas-devel] FriCAS status

FYI, I've done a quick initial Fricas integration test for >which fricas /home/me/TMP/usr/local/bin/fricas >fricas --version FriCAS 2023-06-17 based on sbcl 1.4.16 Using sagemath 10.0 on Linux on first 12 files (1,892 integrals) from CAS integration tests database (these integrals are

Re: [fricas-devel] FriCAS status

On Sat, Jun 24, 2023 at 11:23:32AM -0700, 'Nasser M. Abbasi' via FriCAS - computer algebra system wrote: > Why is this build with sbcl 1.4.6 since there is newer version sbcl 2.3.0? Binary that we distribute is supposed to run on wide range of systems, including older ones. sbcl 1.4.16 makes

Re: [fricas-devel] FriCAS status

On Mon, Jun 19, 2023 at 03:46:34PM +0100, Dima Pasechnik wrote: > On Mon, Jun 19, 2023 at 3:05 PM Waldek Hebisch > wrote: > > > > On Mon, Jun 19, 2023 at 10:29:44AM +0100, Dima Pasechnik wrote: > > > On Mon, Jun 19, 2023 at 8:44 AM Ralf Hemmecke wrote: > > > > > > > > On 19.06.23 09:22, Grégory

Re: [fricas-devel] FriCAS status

Why is this build with sbcl 1.4.6 since there is newer version sbcl 2.3.0? ./fricas --version FriCAS 2023-06-17 based on sbcl 1.4.16 > >fricas --version FriCAS 1.3.8 based on sbcl 2.3.0 > Does it make any difference for performance? I assume the final version of Fricas 1.3.9 will be in source

Re: [fricas-devel] FriCAS status

On Tue, Jun 20, 2023 at 03:28:27AM +0200, Waldek Hebisch wrote: > On Mon, Jun 19, 2023 at 08:33:16AM +0200, Ralf Hemmecke wrote: > > An update to my attempt to build hsbcl on top of sbcl 1.1.1. > > I use the binary sbcl 1.1.1 from sourceforge.net. > > Indeed, there are problems. I am looking at

Re: [fricas-devel] FriCAS status

On Mon, Jun 19, 2023 at 08:33:16AM +0200, Ralf Hemmecke wrote: > An update to my attempt to build hsbcl on top of sbcl 1.1.1. > I use the binary sbcl 1.1.1 from sourceforge.net. Indeed, there are problems. I am looking at possible alternatives and workarounds. --

Re: [fricas-devel] FriCAS status

On Mon, Jun 19, 2023 at 3:05 PM Waldek Hebisch wrote: > > On Mon, Jun 19, 2023 at 10:29:44AM +0100, Dima Pasechnik wrote: > > On Mon, Jun 19, 2023 at 8:44 AM Ralf Hemmecke wrote: > > > > > > On 19.06.23 09:22, Grégory Vanuxem wrote: > > > > I wonder why you're using such an old LISP? > > > > > >

Re: [fricas-devel] FriCAS status

On Mon, Jun 19, 2023 at 10:29:44AM +0100, Dima Pasechnik wrote: > On Mon, Jun 19, 2023 at 8:44 AM Ralf Hemmecke wrote: > > > > On 19.06.23 09:22, Grégory Vanuxem wrote: > > > I wonder why you're using such an old LISP? > > > > Waldek wants to make sure that jfricas also works with the sbcl that

Re: [fricas-devel] FriCAS status

I agree with you Dima, I have even tried to build asdf using quicklisp and it hurts directly with: ; Fetching #http://beta.quicklisp.org/asdf/3.2.1/asdf.lisp;> ; 628.18KB == 643,253 bytes in 0.19 seconds (3254.80KB/sec); ; caught ERROR: ; READ

Re: [fricas-devel] FriCAS status

On Mon, Jun 19, 2023 at 8:44 AM Ralf Hemmecke wrote: > > On 19.06.23 09:22, Grégory Vanuxem wrote: > > I wonder why you're using such an old LISP? > > Waldek wants to make sure that jfricas also works with the sbcl that he > puts into the binary fricas release. In fricas-1.3.8 this was >

Re: [fricas-devel] FriCAS status

On 19.06.23 09:22, Grégory Vanuxem wrote: I wonder why you're using such an old LISP? Waldek wants to make sure that jfricas also works with the sbcl that he puts into the binary fricas release. In fricas-1.3.8 this was sbcl-1.1.1. So I presume that I should test 1.1.1. It seems you have a

Re: [fricas-devel] FriCAS status

Or, with installed 'quicklisp' from Debian, you can look at attached .input file code and remove the different ')lisp ' Le lun. 19 juin 2023 à 09:25, Grégory Vanuxem a écrit : > I forgot, all LISP packages and implementations will be installed in > $HOME/.roswell/ > > Le lun. 19 juin 2023 à

Re: [fricas-devel] FriCAS status

I forgot, all LISP packages and implementations will be installed in $HOME/.roswell/ Le lun. 19 juin 2023 à 09:22, Grégory Vanuxem a écrit : > Hi Ralf, > > I wonder why you're using such an old LISP? It seems you have a x64 > system, why are you not trying roswell for your LISP implementation?

Re: [fricas-devel] FriCAS status

Hi Ralf, I wonder why you're using such an old LISP? It seems you have a x64 system, why are you not trying roswell for your LISP implementation? https://roswell.github.io/ With this very small app, you can easily manage the LISP you want and even add Hunchentoot with just 'ros install

Re: [fricas-devel] FriCAS status

An update to my attempt to build hsbcl on top of sbcl 1.1.1. I use the binary sbcl 1.1.1 from sourceforge.net. sbcl --eval '(load "../la.lisp")' --quit |tee rhxbld.lg This is SBCL 1.1.1, an implementation of ANSI Common Lisp. More information about SBCL is available at .

Re: [fricas-devel] FriCAS status

On Sun, 18 Jun 2023, 17:51 Ralf Hemmecke, wrote: > On 16.06.23 02:14, Waldek Hebisch wrote: > > Well, I wrote "binary". The question is if sbcl version I use for > > creation of binaries has all features needed by jfricas. It should, > > but testing is better than bling faith. > > OK, but

Re: [fricas-devel] FriCAS status

On 16.06.23 02:14, Waldek Hebisch wrote: Well, I wrote "binary". The question is if sbcl version I use for creation of binaries has all features needed by jfricas. It should, but testing is better than bling faith. OK, but building SBCL 1.1.1 from the git repo does not work on my computer.

Re: [fricas-devel] FriCAS status

On Tue, Jun 13, 2023 at 09:40:51PM +0200, Ralf Hemmecke wrote: > On 13.06.23 22:46, hebisch wrote: > > ATM major open thing is inclusion of hunchentoot, I would prefer to > > have confirmation that binary that I create works for jfricas. > > Obviously, Kurt and Qian are currently a bit silent.

Re: [fricas-devel] FriCAS status

On 13.06.23 22:46, hebisch wrote: ATM major open thing is inclusion of hunchentoot, I would prefer to have confirmation that binary that I create works for jfricas. Obviously, Kurt and Qian are currently a bit silent. But you have at least my confirmation. However, I would like to see how you

[fricas-devel] FriCAS status

We have several open bugs and most of things I hoped to do are not done. However, vast majority of bugs is old (present in previous versions) and we have fixes for few problems. So it makes sense to do a new release. ATM major open thing is inclusion of hunchentoot, I would prefer to have

[fricas-devel] FriCAS status

I am thinking about new release somtimes at end of June. Currently number of user visible changes is small, but a few nasty bugs are fixed and we should release the fixes. There is time to include new code and I hope to fix more bugs. -- Waldek Hebisch -- You

Re: [fricas-devel] FriCAS status

Ralf Hemmecke wrote: > > >> Also I think it is better to use ALLOCATE-VECTOR-WITH-WIDETAG > >> than ALLOCATE-VECTOR. > > > > We can not use ALLOCATE-VECTOR-WITH-WIDETAG because it is not > > present in earlier versions of sbcl. > > Cannot this be conditionalized on the version of SBCL that

Re: [fricas-devel] FriCAS status

> > On Fri, May 11, 2018 at 9:47 PM, Waldek Hebisch > wrote: > > oldk1331 wrote: > >> > >> On Fri, Mar 9, 2018 at 9:46 PM, Waldek Hebisch > >> wrote: oldk1331 wrote: > >> > Now all things planned for this release are commited. There > >> >

Re: [fricas-devel] FriCAS status

On Fri, May 11, 2018 at 9:47 PM, Waldek Hebisch wrote: > oldk1331 wrote: >> >> On Fri, Mar 9, 2018 at 9:46 PM, Waldek Hebisch >> wrote: >> > Now all things planned for this release are commited. There >> > is now time for testing. Qian says

[fricas-devel] FriCAS status

>> Also I think it is better to use ALLOCATE-VECTOR-WITH-WIDETAG >> than ALLOCATE-VECTOR. > > We can not use ALLOCATE-VECTOR-WITH-WIDETAG because it is not > present in earlier versions of sbcl. Cannot this be conditionalized on the version of SBCL that FriCAS is compiled for? Ralf -- You

Re: [fricas-devel] FriCAS status

oldk1331 wrote: > > On Fri, Mar 9, 2018 at 9:46 PM, Waldek Hebisch > wrote: > > Now all things planned for this release are commited. There > > is now time for testing. Qian says that 'sbcl_make_sized_vector' > > is buggy -- I will look into this. > > Any update on

Re: [fricas-devel] FriCAS status

On Fri, Mar 9, 2018 at 9:46 PM, Waldek Hebisch wrote: > Now all things planned for this release are commited. There > is now time for testing. Qian says that 'sbcl_make_sized_vector' > is buggy -- I will look into this. Any update on 'sbcl_make_sized_vector'? -- You

Re: [fricas-devel] FriCAS status

On 03/09/2018 09:23 AM, oldk1331 wrote: On Fri, Mar 9, 2018 at 10:20 PM, Raymond Rogers wrote: I will compile on Ubuntu Mint if you like but I need instructions. I tried a complete download but it seems to be the old version. Ray You can either clone the repo

Re: [fricas-devel] FriCAS status

On 03/10/2018 12:02 PM, Waldek Hebisch wrote: Raymond Rogers wrote: This is a multi-part message in MIME format. --2E6B63B7760A09938E7E7BD0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: quoted-printable Hopefully this clip from config.log is

Re: [fricas-devel] FriCAS status

Raymond Rogers wrote: > > This is a multi-part message in MIME format. > --2E6B63B7760A09938E7E7BD0 > Content-Type: text/plain; charset="UTF-8"; format=flowed > Content-Transfer-Encoding: quoted-printable > > > Hopefully this clip from config.log is bogus > > | #define PACKAGE_NAME

Re: [fricas-devel] FriCAS status

Hopefully this clip from config.log is bogus | #define PACKAGE_NAME "FriCAS" | #define PACKAGE_TARNAME "fricas" | #define PACKAGE_VERSION "2017-08-05" | #define PACKAGE_STRING "FriCAS 2017-08-05" | #define PACKAGE_BUGREPORT "fricas-devel@googlegroups.com" | #define PACKAGE_URL "" Because the

Re: [fricas-devel] FriCAS status

> > make failed.  If you want the resulting config.log and/or "make > >make.lst" let me know how you want them. First, which versions did you use? That is 'sbcl' version, Ubuntu version, etc? -- Waldek Hebisch -- You received this message because you are

Re: [fricas-devel] FriCAS status

make failed.  If you want the resulting config.log and/or "make >make.lst" let me know how you want them. -- tail end of make.lst    finalizing NRLIB MODFACT    Processing ModularFactorization for Browser database: constructor-

Re: [fricas-devel] FriCAS status

On Fri, Mar 9, 2018 at 10:20 PM, Raymond Rogers wrote: > I will compile on Ubuntu Mint if you like but I need instructions. I tried > a complete download but it seems to be the old version. > > Ray > You can either clone the repo by svn or git, or download a most

Re: [fricas-devel] FriCAS status

I will compile on Ubuntu Mint if you like but I need instructions.  I tried a complete download but it seems to be the old version. Ray On 03/09/2018 08:46 AM, Waldek Hebisch wrote: Now all things planned for this release are commited. There is now time for testing. Qian says that

[fricas-devel] FriCAS status

Now all things planned for this release are commited. There is now time for testing. Qian says that 'sbcl_make_sized_vector' is buggy -- I will look into this. Anyway, if major new problems show up (including build failures) we will fix them. Otherwise the release will be from current svn. --

Re: [fricas-devel] FriCAS status

I agree. On Mar 2, 2018 10:46 PM, "Waldek Hebisch" wrote: Concerning other Texmacs patches: 1) I Wanted to commit first 5 or 6 patches, but ATM Sourceforge does not work. 2) the 'fricasintexmacs' completely go against name conventions in FriCAS. Some Lisps insits that

Re: [fricas-devel] FriCAS status

Concerning other Texmacs patches: 1) I Wanted to commit first 5 or 6 patches, but ATM Sourceforge does not work. 2) the 'fricasintexmacs' completely go against name conventions in FriCAS. Some Lisps insits that global variables are "intrusively special" which risks unintended name capture. Due

Re: [fricas-devel] FriCAS status

> > On Thu, Mar 1, 2018 at 11:47 PM, Waldek Hebisch > wrote: > > oldk1331 wrote: > >> > >> Hi Waldek, you haven't commented on the following patches. > >> Also, please merge the documentation fix patches as long as > >> you see fit. > >> > >> > fix display of 'box': >

Re: [fricas-devel] FriCAS status

On Thu, Mar 1, 2018 at 11:47 PM, Waldek Hebisch wrote: > oldk1331 wrote: >> >> Hi Waldek, you haven't commented on the following patches. >> Also, please merge the documentation fix patches as long as >> you see fit. >> >> > fix display of 'box': >> > >> >

Re: [fricas-devel] FriCAS status

oldk1331 wrote: > > Hi Waldek, you haven't commented on the following patches. > Also, please merge the documentation fix patches as long as > you see fit. > > > fix display of 'box': > > > > https://github.com/oldk1331/fricas/commit/2c02ad4ea19d7869327ed708a5e8ff93fd6bfc29.patch This is a

Re: [fricas-devel] FriCAS status

Hi Waldek, you haven't commented on the following patches. Also, please merge the documentation fix patches as long as you see fit. > fix display of 'box': > > https://github.com/oldk1331/fricas/commit/2c02ad4ea19d7869327ed708a5e8ff93fd6bfc29.patch > > fix PostScript format image output: > >

Re: [fricas-devel] FriCAS status

On Mon, Feb 26, 2018 at 8:56 PM, Waldek Hebisch wrote: >> >> And another bug fix: >> >> fix ^ : (%, NNI) -> % in Factored >> >> test case: "factor(6)^0" returns "1" instead of "2^0*3^0" > > AFAICS "1" is the correct result. What you propose would Yes, I mean after my

Re: [fricas-devel] FriCAS status

oldk1331 wrote: > > On Mon, Feb 26, 2018 at 2:35 AM, Waldek Hebisch > > >> I wish my 10 patches that imporves the TeXmacs interface > >> could also get merged, so that I can upstream relevant > >> parts to TeXmacs project. > > > > Which ones? I see 7 patches marked "texmacs". I looked at > >

Re: [fricas-devel] FriCAS status

On Mon, Feb 26, 2018 at 2:35 AM, Waldek Hebisch wrote: > oldk1331 wrote: >> >> I would like to include these patches also: >> >> >> compiler gives error on non-exist imports: >> >> https://github.com/oldk1331/fricas/commit/89dd2e8008602ed00cf1f13fe0d75c50205cbfcc.patch >

Re: [fricas-devel] FriCAS status

oldk1331 wrote: > > I would like to include these patches also: > > > compiler gives error on non-exist imports: > > https://github.com/oldk1331/fricas/commit/89dd2e8008602ed00cf1f13fe0d75c50205cbfcc.patch Eliminating non-existing imports is nice. But the change to compiler looks fragile, it

Re: [fricas-devel] FriCAS status

I would like to include these patches also: compiler gives error on non-exist imports: https://github.com/oldk1331/fricas/commit/89dd2e8008602ed00cf1f13fe0d75c50205cbfcc.patch fix input/fns.input: https://github.com/oldk1331/fricas/commit/1c589fe749c4d9f59b35ef2cc038d77fed33dfda.patch I

Re: [fricas-devel] FriCAS status

Typo fixes in previous commits: diff --git a/ChangeLog b/ChangeLog index 50f4eaf9..00a725e4 100644 --- a/ChangeLog +++ b/ChangeLog @@ -22,7 +22,7 @@ 2018-02-21 Waldek Hebisch * src/interp/br-con.boot, src/interp/br-op2.boot, - src/interp/daase.lisp: Misc clenups +

Re: [fricas-devel] FriCAS status

On 02/22/2018 01:41 AM, oldk1331 wrote: >>> fix documentation in aggcat.spad: >>> >>> https://github.com/oldk1331/fricas/commit/2be927aabf94ca05be45444027c12ef5172cd122.patch >> AFAICS '==' in original was used to get valid Spad function definition. >> I am not sure if we want to replace this by

Re: [fricas-devel] FriCAS status

On Thu, Feb 22, 2018 at 5:19 AM, Waldek Hebisch wrote: > oldk1331 wrote: >> >> fix 'leaf?' in URAGG: >> >> https://github.com/oldk1331/fricas/commit/4aea91d7b209d856dca09569c8dc53370769f48e.patch > > For this we need to think about definitions. My first impulse is > to

Re: [fricas-devel] FriCAS status

oldk1331 wrote: > > fix 'leaf?' in URAGG: > > https://github.com/oldk1331/fricas/commit/4aea91d7b209d856dca09569c8dc53370769f48e.patch For this we need to think about definitions. My first impulse is to say that leaf is node with no children, so in particular not empty... > > fix recursive

Re: [fricas-devel] FriCAS status

doc cleanup: https://github.com/oldk1331/fricas/commit/119ef3df12f9347aa7dcbadd0e565ed1ca09a886.patch doc fix: https://github.com/oldk1331/fricas/commit/77195e530cc5c7e58f98ef265ee307c8577c3c36.patch fix 'leaf?' in URAGG:

Re: [fricas-devel] FriCAS status

oldk1331 wrote: > > I have 164 commits in > > https://github.com/oldk1331/fricas/commits/mymaster2 > > most of them are ready to be merged. > > How would you like to proceed? I took quick look at them. Does WIP mean "Work in Progress"? Some your changes look debatable. Obviously correct

Re: [fricas-devel] FriCAS status

Riccardo Guida wrote: > > Wish: If you plan to release binaries, would it be possible to compile and > release in some contrib directory also the binaries of Kurt Parentani's > fricas_jupyter [1] ... if the code works and Kurt agrees, I mean. > > Regards Riccardo > > [1]

Re: [fricas-devel] FriCAS status

Although, I will probably try to make fricas_jupyter work for me with every local change to my git repository, I think it would be a nice thing to integrate a modern interface to FriCAS and make it available to a broader user base. Maybe in the first round we can declare it to be experimental.

Re: [fricas-devel] FriCAS status

On Tue, Feb 20, 2018 at 6:13 AM, wrote: > Wish: If you plan to release binaries, would it be possible to compile > and release in some contrib directory also the binaries of Kurt > Parentani's fricas_jupyter [1] ... if the code works and Kurt agrees, > I mean. > ++1

Re: [fricas-devel] FriCAS status

Hello Waldek Wish: If you plan to release binaries, would it be possible to compile and release in some contrib directory also the binaries of Kurt Parentani's fricas_jupyter [1] ... if the code works and Kurt agrees, I mean. Regards Riccardo [1] https://github.com/nilqed/fricas_jupyter --

Re: [fricas-devel] FriCAS status

I have 164 commits in https://github.com/oldk1331/fricas/commits/mymaster2 most of them are ready to be merged. How would you like to proceed? On Tue, Feb 20, 2018 at 1:03 AM, Waldek Hebisch wrote: > I think it is time for new release. We have several open >

[fricas-devel] FriCAS status

I think it is time for new release. We have several open bugs but most are old and we can not expect quick resolution. In period from last release we accumulated several bug fixes and new code. I intend spent next two weeks on some more bugs fixes and workarounds. Also, I will try to include

Re: [fricas-devel] FriCAS status

BTW, the man page is recently added because of Debian packaging? It should get installed by Makefile. -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: [fricas-devel] FriCAS status

The FriCAS VERSION hasn't been updated for a long time: FriCAS Computer Algebra System Version: FriCAS 2016-08-28 -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To

Re: [fricas-devel] FriCAS status

Will you include the doc fixes I posted in April 16? BTW, I think the release process is a bit too long -- almost a month! -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving

[fricas-devel] FriCAS status

At http://www.math.uni.wroc.pl/~hebisch/fricas/fricas-1.3.2-pre.tar.bz2 I have put a prelimiary testing tarball -- hopefuly new relase will differ only in version number. The release itself will be in few days. -- Waldek Hebisch -- You received this message

Re: [fricas-devel] FriCAS status

oldk1331 wrote: > > Do you plan to do the release this week? > I'd hope some bug fixes can be merged before release. Yes. ATM there is problem with building Aldor interface, that is most serious problem waiting for resolution. There is bunch of other serious problems, but resolving them would

Re: [fricas-devel] FriCAS status

Do you plan to do the release this week? I'd hope some bug fixes can be merged before release. -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email

Re: [fricas-devel] FriCAS status

I think there are about 10 patches still pending? Other than that, there are a few difficult bugs: integrate((f^2 + x^2)/((x - a)* (x - b)* (x - c)* (x - d)),x) Add Algebra Integer to Ring doesn't compile. Problem with 'has', 'evalDomainOpPred'. Are they expected to be fixed in this release?

[fricas-devel] FriCAS status

I am thinking about new release in about 2-3 weeks. Previous releases took quite long, it is better to release early. -- Waldek Hebisch -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To

Re: [fricas-devel] FriCAS status

I have now created a release branch. Unless there are serious problems this is going to be next release. As I wrote we recently learned about several integration bugs and we had a few long standing ones. Most is now fixed or worked around, but w a few remain. Also I postponed including some

Re: [fricas-devel] FriCAS status

> Probably. The patches looked good, but you lost me what > is the final version. I'll post a (current) final version in another thread. > Concerning independent variable, > as I wrote I do not see strong reason to have it as > part IntegrationResult and trying to add it would be > a risky

Re: [fricas-devel] FriCAS status

oldk1331 wrote: > > > ATM I am looking at the bugs, but I consder shipping next > > release without fixing them. More precisely, randomness > > workaround is rather safe so we could ship it. But > > properly handling other issues may delay release too > > much. > > This will be a maintenance

Re: [fricas-devel] FriCAS status

> ATM I am looking at the bugs, but I consder shipping next > release without fixing them. More precisely, randomness > workaround is rather safe so we could ship it. But > properly handling other issues may delay release too > much. This will be a maintenance release, version will be 1.3.1? Do

[fricas-devel] FriCAS status

Currently most things planned for next release is done. However, there are several problems with integration of algebraic functions: - at least two bugs with handling algebraic constants during integration (I have fixes for two) - the possibleOrder routine sometimes returns wrong order (this

Re: [fricas-devel] FriCAS status

> > On Mon, 16 Jan 2017, Waldek Hebisch wrote: > > It is time to think about new FriCAS release. > It would be good to ensure that it compiles with the latest sbcl-1.3.13. Yes. I can compile with sbcl-1.3.13 now but I need to check alternatives and do measurements to find the best way. --

Re: [fricas-devel] FriCAS status

On 01/16/2017 01:30 PM, Waldek Hebisch wrote: There are also improvements that I would like to add (in particular I have to look at Martin's Baker patch). Yes, there are 2 outstanding patches. The first one is here: https://groups.google.com/forum/?hl=en#!topic/fricas-devel/EtLwgd2dWNU This

Re: [fricas-devel] FriCAS status

On Mon, 16 Jan 2017, Waldek Hebisch wrote: It is time to think about new FriCAS release. It would be good to ensure that it compiles with the latest sbcl-1.3.13. Andrey -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To

Re: [fricas-devel] FriCAS status

On 01/16/2017 02:30 PM, Waldek Hebisch wrote: > - Building Aldor interface fails. This is about to be fixed. Basically Peter Broadbery did the work, but because of illness I haven't yet tested and put everything together as a proper patch. Ralf -- You received this message because you are

  1   2   >