> I wanted to avoid useless talk in the README. I am affraid that > "parametric dependent types" does not tell much for many our > potential readers. And some folks may understand it wrong.
OK. Let's settle it and let it be "strongly typed". > Formally it can be argued that Spad type system is in its own > category, different from usual dynamic/static distinction. > Namely types are runtime objects but are associated with > variables. Usual dynamic typing associates types with data, > which is quite different. OTOH, classic static type system > require all type info to be compile-type computable. SML > and followers weakens compile-type computable to compile-type > checkable, but stil requires that one can discard type info > before runtime. Spad is mostly compile-time checkable, but some > checks must be done at runtime and more importantly, types > are needed at runtime. Yes, it would make sense to put such information somewhere. I have written https://fricas.github.io/fricas-notebooks/FriCAS-Types.html However, that was more intended for end-users that are not experts in classification of programming languages. Maybe it would fit at the very end of it to explain the specific way of how types are designed in FriCAS. Maybe, it would even be better to have such information here https://hemmecke.github.io/fricas/features.html or as a subpage of it. In fact, the intention of "Features" is to list all important things of FriCAS. In particular, it might be useful to list a few things that other CAS do not have, so in some sense that page might help people writing for wikipedia to easily compare to other CAS. >> README.rst will not go through sphinx. I is just rendered by github. > Well, "retext" is claimed to be an editor, I do not want editor, I just use it for a simple check. > I want something to check that README does not contain formatting > blunders. Wikipedia says that Restructured Text is "sphinx" > format, so it looked natural to use "sphinx" as checker. If > github (or maybe other "sphinx" version) renders it differently, > then we have a problem... I guess that correct .rst files will produce the same output. If incorrect .rst files give different output in different renderes, that's not a problem of reStrucutredText. Sphinx should be OK. See https://hemmecke.github.io/fricas/_sources/features.rst.txt and https://hemmecke.github.io/fricas/features.html These sources went through sphinx and look OK. 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/3bb106b8-ef17-de55-15c4-a6f030adc227%40hemmecke.org.
