There are other things to write about but first just a note about
LLVM. I have been following a project called CLASP
https://github.com/drmeister/clasp . It is still rather pre-beta with
a fairly slow but steady rate of development but in principle might
eventually be a path from *AXIOM to LLVM. I understand however that
you are targeting LLVM more directly so I am not sure if CLASP is at
all relevant to you.

In terms of algebra I am still keen to implement some kind of
generalization of the Expression domain to encompass first of all a
major part of non-commutative involutive algebra
https://en.wikipedia.org/wiki/*-algebra . My motivation actually
originates with a desire to implement Wirtinger Calculus./CR-calculus
and some other features relating to the handling of general
complex-valued functions. If this is done in what I consider the
correct and "deep" manner it would have major implications for the
structure of the Axiom library.  I have some work in FriCAS here:
https://github.com/billpage/fricas/tree/CR-calculus and some more
here: http://axiom-wiki.newsynthesis.org/SandBoxWirtinger but Waldek
raised a number of very reasonable "objections in principle" to what I
was doing and which I could not immediately answer so I started to
loose focus on this work.

More recently and new contributor to FriCAS re-kindled an interest in
Monads in Axiom and in particular the work you did several years ago
on Maybe in OpenAxiom.  It seems there are significant limitations in
the Axiom/FriCAS implementation of SPAD that have (largely) been over
come in OpenAxiom. This is one thing in particular that recalled my
interesting in doing more in OpenAxiom. I am particularly interested
in the 'forall' quantifier extensions that allow many artificial uses
of the Package construct to be replaced with much clearer and more
compact code.  So I am very interested to see what other features of
this type.in OpenAxiom you might be planning.

The code for my work on the OpenAxiom gui is here:
https://github.com/billpage/open-axiom/tree/gui-latex/wip with my last
commit on April 7.  I think this still builds and works but in the end
I was not completely satisfied with the result.  After learning a lot
more than I really wanted to about the QTTextDocument and QTTextEdit
classes http://doc.qt.io/qt-5/richtext.html I started to think that
maybe an overall better approach would be to implement the gui
worksheet as a single QT document and then integrate OpenAxiom as a
custom text object http://doc.qt.io/qt-5/qtextobjectinterface.html . I
was very impressed that it was possible to embed such a richly
featured text editor into a QT application. The advantage would be
immediate access to some rather sophisticated high-level tools for
saving and loading documents as well as producing PDF and HTML
outputs.

Best wishes for the New Year.

Bill Page.

On 26 December 2016 at 10:54, Gabriel Dos Reis
<g...@integrable-solutions.net> wrote:
> Hi Bill,
>
> Happy holidays to you and everybody!
>
> I have not done as much as I wish on OpenAxiom this year.  However, it is
> not dead :-)
> I am very much open to experiments in OpenAxiom and branches.
>
> There are quite a few things I would like to do in the coming months:
>    * Make OpenAxiom less reliant on Lisp, and more native, possibly with an
> LLVM backend.  LLVM is available on more platforms (I care about) than Lisp
> is.  The major downside with LLVM, of course, is its policy of frequent API
> breaking changes.
>
>    * More algebra work -- this may require more core language work and more
> build system work.  As you know, OpenAxiom can bootstrap without cached Lisp
> intermediate files.  Also, I believe OpenAxiom no longer needs an existing
> domain database when bootstrapping.  That means making changes to the
> algebra is now easier.  There may be a few kinks to work out.
>
>   * Make OpenAxiom buildable again on Windows platforms.  A some point, we
> lost that ability, I don't know what happened.  That is ironic given my
> daytime occupation. :-)  I want to accomplish an integration with VS Code to
> allow better experience.  I would love to see what you did with your
> QT-based project here.
>
> I have more projects in mind, but for the coming year I think this will do,
> given my track record :-)
>
> -- Gaby
>
>
> On Mon, Dec 26, 2016 at 7:07 AM, Bill Page <bill.p...@newsynthesis.org>
> wrote:
>>
>> Gaby,
>>
>> I noticed a recent commit to OpenAxiom on GitHub and it reminded me of
>> my New Year's resolution to do more work with Axiom. I did some work
>> early-on this year with OpenAxiom QT gui interface (adding LaTeX
>> output and extending various features like document save/load, etc.)
>> but I did not quite get to the point of making a pull request. Coding
>> in QT was a "learning experience" ... There are also a number of
>> projects and experiments on the algebra side for most of which I have
>> to used FriCAS or Sage. I began to realize that many of the features I
>> was missing in FriCAS already existed in OpenAxiom and it occurred to
>> me that perhaps I should change my focus.
>>
>> I was wondering if you have specific plans for OpenAxiom in the coming
>> year and whether you would be interested in work that I might commit?
>>
>> Thanks and Happy New Year.
>>
>> Bill Page.
>>
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
open-axiom-devel mailing list
open-axiom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel

Reply via email to