Ralf Hemmecke wrote:
>
> Hi Waldek,
>
> in your most recent patch you've restructured outputTran and added
> outputTran2.
>
> Any particular reason why you haven't simply renamed the old outputTran
> to outputTran2 and called the new one outputTran? That would have
> avoided to change code in other files (in particular the .spad files.
No strong reason. I just did that in incremental way and at the
start outputTran2 was tiny and called only from two places...
>
> Am I right that currently we have
>
> outputTran2 used for transformation of algebraic structures
> (BRACKET, SEGMENT, MINUS, *, etc.)
> outputTran used for transformation of programming structures
> (IF, REPEAT, COLLECT, etc.
That is the intended division.
> Hmm... cannot be right, because I also see BRACE, LIST, and matrix in
> outputTran.
Well, LIST is not a valid OutputForm operator, but a valid Lisp
function. Normaly operators in OutputForm are uppercase, so
for matrices it is 'MATRIX'. It it possible that I missed
some operator and it should go from 'outputTran' to 'outputTran2'.
It is also possible that 'outputTran' contains some old things
that are no longer in use. The point is that 'outputTran' is
called on code and _all_ code is supposed to go trough 'outputTran'
as part of generating OutputForm. So routines transforming
OutputForm should not be bothered by code constructs. All
code specific things should be translated to regular OutputForm
in 'outputTran'. Thanks to this we are getting closer to the
point when we can freely change representation of OutputForm.
--
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.
