On Fri, 23 Jan 2026 at 12:23, Kurt Pagani <[email protected]> wrote: > > Cool, quite impressive, thanks :) > > I asked two questions: > * Do you know the connection with aldor? > * Is it feasible to port fricas completely to aldor (instead of > common-lisp based)? > > > a tiny snippet out of the comprehensive answers > "" > Based on the codebase, porting FriCAS completely to Aldor instead of > Common Lisp would be theoretically possible but practically infeasible > due to the deep architectural dependencies on Lisp throughout the system. > "" > > I also think so. Only recently I tinkered with the aldor interpreter and > have to conclude that it would need enormous effort to obtain a > comparable environment like current fricas is offering. > > I made a clang/scan-build of aldor > (https://nilqed.github.io/aldor-scan-build/) and could fix some > SEGFAULTS and included some more #int options in order to change > appearance (prompt/type display) so it looks more like fricas. However, > similar look doesn't mean similar behavior ;) > > (see https://github.com/nilqed/aldor/tree/nilqed)
This looks useful - the main changes could go into the main code base if you're happy with that. (Since I don't use the interpreter mode much, any improvements and ideas are appreciated) The clang scan looks good as well - I'll look into getting rid of the easier issues. Thanks, Peter -- 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 to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/fricas-devel/CAK%3DmBN8-0D%2BtkY50QmjRuZrdHKwm-g%3Dbb%2BzkWCEuk5%3DmRTJfWg%40mail.gmail.com.
