On 30/07/16 03:53, oldk1331 wrote:
Everyone, poll:

Do you have a private bug list? If so, how many bugs?

No, I find simple definite bugs tend to get fixed if reported here.

For instance the bug in spanningTree in graph.spad I'm hoping that Waldek will apply my fix when I sort out the other issues in that file.

It seems to me that there are more problems when an issue is on the boundary between bug or feature request.

For example in Clifford algebra, since the same operators are used for logic. FriCAS allows me to type in an expression like A/\B*C/\D and it gets the result wrong:

(A/\B)*(C/\D)  -- is what I expected
((A/\B)*C)/\D  -- is what I got

This is a serous problem for Clifford algebra which severely limits its usefulness. However SPAD is working as it is supposed to, the problem is an incompatibility between infix operator precedence between Clifford and logic code.

So is this a bug?

Another issue is documentation and error messages. For instance, if I were to get '$' where FriCAS now uses '%'. At that time I would be debugging my own code so I might make a mental note to report it but then forget.

Also error messages tend to use the word 'mode' where I think the word 'type' would be more appropriate. It may be that the word 'mode' is more appropriate to users who know the internal workings of the lisp code but is this a requirement for every user?

Is this a bug?

I think all of these things are bugs because they confuse and put off potential users of FriCAS.

However would a more formal bug tracker help with any of these issues? I suspect not because it would just take up peoples time to report and administer bugs that are not likely to be fixed?

Martin B

--
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.

Reply via email to