Repeatedly it is raised as an issue that our OutputForm is
lossy. Main source of loss is identity of variables, that
is information to which domain belongs given variable.
It seems that at OutputForm level we could solve this
problem by introducing we construct, let me call it
BINDING. BINDING would establish a scope ad tell that
given variable belongs to this scope. Inner BINDING
could use the same variable name and thanks to known
scope avoid unintended conflict of names. Of course
to do any good this construct needs support in
formatters. Trivial support would just erase BINDING-s
giving current output. Smarter support could do
some renaming to avoid conflicts.
Important point is that when we generate OutputForm
we do not know all names, so at that stage renaming
is inpractical. But we know scope so can indicate this.
--
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.