Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Rightclick on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
From: <noreply@so...>  20021028 08:37:56

Bugs item #629716, was opened at 20021028 03:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=629716&group_id=4933 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stavros Macrakis (macrakis) Assigned to: Nobody/Anonymous (nobody) Summary: dotexptsimp and x^^2/FIX Initial Comment: In general, dotexptsimp:false inside Expand expands out noncommutative powers to noncommutative products, e.g. dotexptsimp:false; expand((x.y)^^2) => x.y.x.y But not always: dotexptsimp:false expand(x^^2) => x^^2 and dotexptsimp:false expand(x.y^^2) => x.y^^2 This makes it impossible (?) to simplify (x.y)^^2 . y  x.y.x.y^^2 to zero. There is a simple patch for this, which makes expand (x^^3) => x.x.x (if dotexptsimp:false). I wonder if that will cause problems anywhere else? Here's the patch. In simpncexpt, just remove the mnctimesp test in the two tests which read as follows: ((and (or (mplusp factor) (and (not $dotexptsimp) (mnctimesp factor))) ....  You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=629716&group_id=4933 
From: SourceForge.net <noreply@so...>  20060827 00:24:13

Bugs item #629716, was opened at 20021028 01:37 Message generated for change (Settings changed) made by robert_dodier You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=629716&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  Simplification Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stavros Macrakis (macrakis) Assigned to: Nobody/Anonymous (nobody) Summary: dotexptsimp and x^^2/FIX Initial Comment: In general, dotexptsimp:false inside Expand expands out noncommutative powers to noncommutative products, e.g. dotexptsimp:false; expand((x.y)^^2) => x.y.x.y But not always: dotexptsimp:false expand(x^^2) => x^^2 and dotexptsimp:false expand(x.y^^2) => x.y^^2 This makes it impossible (?) to simplify (x.y)^^2 . y  x.y.x.y^^2 to zero. There is a simple patch for this, which makes expand (x^^3) => x.x.x (if dotexptsimp:false). I wonder if that will cause problems anywhere else? Here's the patch. In simpncexpt, just remove the mnctimesp test in the two tests which read as follows: ((and (or (mplusp factor) (and (not $dotexptsimp) (mnctimesp factor))) ....  You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=629716&group_id=4933 
From: SourceForge.net <noreply@so...>  20060909 15:11:04

Bugs item #629716, was opened at 20021028 01:37 Message generated for change (Settings changed) made by robert_dodier You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=629716&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  Simplification >Group: Includes proposed fix Status: Open Resolution: None Priority: 5 Submitted By: Stavros Macrakis (macrakis) Assigned to: Nobody/Anonymous (nobody) Summary: dotexptsimp and x^^2/FIX Initial Comment: In general, dotexptsimp:false inside Expand expands out noncommutative powers to noncommutative products, e.g. dotexptsimp:false; expand((x.y)^^2) => x.y.x.y But not always: dotexptsimp:false expand(x^^2) => x^^2 and dotexptsimp:false expand(x.y^^2) => x.y^^2 This makes it impossible (?) to simplify (x.y)^^2 . y  x.y.x.y^^2 to zero. There is a simple patch for this, which makes expand (x^^3) => x.x.x (if dotexptsimp:false). I wonder if that will cause problems anywhere else? Here's the patch. In simpncexpt, just remove the mnctimesp test in the two tests which read as follows: ((and (or (mplusp factor) (and (not $dotexptsimp) (mnctimesp factor))) ....  You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=629716&group_id=4933 
From: SourceForge.net <noreply@so...>  20070131 20:37:24

Bugs item #629716, was opened at 20021028 02:37 Message generated for change (Comment added) made by willisbl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=629716&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  Simplification Group: Includes proposed fix >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Stavros Macrakis (macrakis) Assigned to: Nobody/Anonymous (nobody) Summary: dotexptsimp and x^^2/FIX Initial Comment: In general, dotexptsimp:false inside Expand expands out noncommutative powers to noncommutative products, e.g. dotexptsimp:false; expand((x.y)^^2) => x.y.x.y But not always: dotexptsimp:false expand(x^^2) => x^^2 and dotexptsimp:false expand(x.y^^2) => x.y^^2 This makes it impossible (?) to simplify (x.y)^^2 . y  x.y.x.y^^2 to zero. There is a simple patch for this, which makes expand (x^^3) => x.x.x (if dotexptsimp:false). I wonder if that will cause problems anywhere else? Here's the patch. In simpncexpt, just remove the mnctimesp test in the two tests which read as follows: ((and (or (mplusp factor) (and (not $dotexptsimp) (mnctimesp factor))) ....  >Comment By: Barton Willis (willisbl) Date: 20070131 14:37 Message: Logged In: YES user_id=895922 Originator: NO Suggested fix applied (mdot.lisp CVS r 1.4). Also appended new regression test for this bug (rtest_dot.mac).  You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=629716&group_id=4933 
Sign up for the SourceForge newsletter:
No, thanks