Martin Rubey <[email protected]> writes: > I found a bug in unparse:
> I believe the bug is in form2String1, format.boot, where the function > SEGMENT is given special treatment: > > -------------------------------------------------------------------------- > form2String1 u == > > ... > op = "SEGMENT" => > null argl => '".." > lo := form2String1 first argl > argl := rest argl > (null argl) or null (first argl) => [lo, '".."] > [lo, '"..", form2String1 first argl] ... > application2String(op,[form2String1 x for x in argl], u1) > -------------------------------------------------------------------------- Well, it's not in form2String1, but rather in application2String. I removed both, and now things seem to work fine. I'll do some checking, and commit if nobody complains. -- I think in general it's better to have unparse output explicit function calls, and rather prefix notation than infix. Martin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
