From: SourceForge.net <no...@so...> - 2006-07-01 04:40:20
|
Bugs item #643254, was opened at 2002-11-24 15:11 Message generated for change (Comment added) made by robert_dodier You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=643254&group_id=4933 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Lisp Core Group: None Status: Open Resolution: None Priority: 5 Submitted By: Barton Willis (willisb) Assigned to: Nobody/Anonymous (nobody) Summary: orderlessp([rat(x)], [rat(x)]) Initial Comment: The orderlessp function often halts with a (non-descriptive) error message if one or more of its arguments are lists or matrices containing CRE expressions. The Maxima documentation for orderlessp doesn't mention this limitation. If you need to order expressions that might involve lists or matrices containing CRE expressions, apply totaldisrep to each argument of the ordering predicate. Here's an example Maxima 5.5 Tue Dec 5 16:55:33 2000 (with enhancements by W. Schelter). Licensed under the GNU Public License (see file COPYING) (C4) xorderlessp(x,y) := orderlessp(totaldisrep(x), totaldisrep(y)); (D4) xorderlessp(x, y) := ORDERLESSP(TOTALDISREP(x), TOTALDISREP(y)) /* xorderlessp works okay on lists with CRE elements */ (C5) xorderlessp([rat(x)],[rat(x)]); (D5) FALSE (C6) orderlessp([rat(x)], [rat(x)]); Error: 1 is not of type LIST. Fast links are on: do (si::use-fast-links nil) for debugging Error signalled by MACSYMA-TOP-LEVEL. Broken at MACSYMA-TOP-LEVEL. Type :H for Help. MAXIMA>> Either the documentation should warn the user not to use orderlessp or ordergreatp on lists or matrices that contain CRE elements, or these functions should apply totaldisrep to each argument. Barton ---------------------------------------------------------------------- >Comment By: Robert Dodier (robert_dodier) Date: 2006-06-30 22:40 Message: Logged In: YES user_id=501686 Still present in 5.9.3cvs. Right thing to do here is to have GREAT apply totaldisrep. Even better would be to give CRE's a representation which doesn't require special cases scattered through the entire codebase. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=643254&group_id=4933 |