> It seems Fricas is similar to Python in this, in that it uses spaces and > indentations for when a construct end.
Right. > I do not like this myself. I think having an explicit *end* make the code > and the algorithm more clear, instead of just depending on using spaces. I am actually on your side and used C-style coding in Aldor (which was invented to become the new compiler in AXIOM when AXIOM was still a commercial product, but unfortunately never made it into the system. So the situation now is that we have to live with what we have in FriCAS. > I know very little about programming in Fricas. Is this the only mode of > programming in Fricas? Why not have an explicit end? Was this a choice > made long time ago for the Fricas language? The closest you can get is to enclose code blocks in parentheses and separate command by ; (semicolon). if h > 3.1 then 1.0 else (z := cos(h); max (z ,0.5)) I don't think that it is much better with parentheses. You will soon get along with pile mode if you exercise programming a bit. Ralf -- 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 on the web visit https://groups.google.com/d/msgid/fricas-devel/de9659ce-79e6-73b6-b46a-94fcd19cbc79%40hemmecke.org.
