On Mon, Feb 17, 2020 at 05:44:03PM +0100, Kurt Pagani wrote:
> Below are some 'losses' I encounter when compiling (older) code from other
> people:
>
> OrderedFreeMonoid
> FreeAbelianMonoidCategory
> InnerFreeAbelianMonoid
> FreeAbelianMonoid
> FreeAbelianGroup
> Monad was renamed to Magma
> Magma was renamed to FreeMagma
> lo => low
> hi => high
>
> VectorSpace ;)
>
> Usually, some macros allow compilation without changes in the sources. There
> are
> certainly not so many as I've thought, so it wouldn't justify a special
> compatibility package (e.g. like in python2/3).
Most changes are to clean up things are reduce confusion. If
something is useful enough to warrant a compatibility packge,
then in most cases it would be wiser not to remove it at all.
And that is purpose of discussion like this: are there good
reasons to keep things like the above (well, Monad and Magma
above are exceptions, we had to switch to better naming).
For example, in case of VectorSpace, part of cost of keeping it
is that documentation must then explan:
No, despite promising name VectorSpace is not right thing here,
you should use Module instead.
It is clearer to say:
There are not such thing as VectorSpace, in FriCAS you
use Module.
--
Waldek Hebisch
--
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/20200219153323.GA27789%40math.uni.wroc.pl.
