Given that there is workaraund using package call I think that we can keep your fixes and update ideal.input.pamphlet to use package call (so that test pass).
Does that mean I should commit my package call patch? http://groups.google.com/group/fricas-devel/msg/efebd3dec4ae18b1
But we also need a test for this kind of call, that is new bugs2012 file and a short test marked as expected failure.
Or do you want to do this yourself in connection with adding bugs2012?
More generaly, if a fix triggers a problem we need to think twice before commiting a fix, even if core reason of the new problem is outside of the fix. Simply, type discipline is to get more reliable code at the end. If we allow breakage to get in at the end of day it may happen that our "better" code actually works worse than original. Note also that broken code is harder to test, so more breakage is likely to follow because of limited testing.
I'm sorry that I missed that failing test. I promise to run norm-output next time. I agree that "better" is not necessarily better.
Ralf -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fricas-devel?hl=en.
