>
> Interesting, the function
>
> convert: (OutputForm, Integer, OutputForm) -> %
>
> is actually nowhere implemented in TexFormat.
>
> Also
>
> =: (%, %) -> Boolean
> hashUpdate!: (HashState, %) -> HashState
>
> are missing.
>
> In fact, I don't see a reason why TexFormat must export SetCategory.
>
> Opinions?
AFAICS currently coercion from TexFormat to OutputForm is used
for debugging purposes. So we could replace SetCategory by
CoercibleTo(OutputForm).
Concerning 'convert' above we probably could remove it from
exported signatures. My guess is that this 'convert' was
intended to be part of "Saturn" interface. We probably do
not have manpower to reconstruct "Saturn" design (and
volunteers typically prefer working on new designs).
Anyway, adding exported signatures is easy, so removal
is easy to undo if/when somebody wants to implement
such a function.
--
Waldek Hebisch
[email protected]
--
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 http://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.
