Open rtoy opened 5 days ago
Imported from SourceForge on 2024-07-04 15:08:22 Created by willisbl on 2007-05-07 11:11:11 Original: https://sourceforge.net/p/maxima/bugs/1188/#e78c
Logged In: YES user_id=895922 Originator: YES
See also bug 887639.
Imported from SourceForge on 2024-07-04 15:08:25 Created by robert_dodier on 2022-09-23 02:20:43 Original: https://sourceforge.net/p/maxima/bugs/1188/#1b54
Imported from SourceForge on 2024-07-04 15:08:29 Created by robert_dodier on 2022-09-23 02:20:43 Original: https://sourceforge.net/p/maxima/bugs/1188/#8caf
Bugs mentioned above are still present in 5.46+.
"Fast" arrays are CL hash tables in the value slot -- the errors triggered by the example above probably stem from assuming that too-narrow assumptions about what kinds of things we're looking at.
Imported from SourceForge on 2024-07-04 15:08:32 Created by macrakis on 2022-09-23 14:48:31 Original: https://sourceforge.net/p/maxima/bugs/1188/#85ab
The array features of Maxima are a royal mess, without consistent semantics or UI. use_fast_arrays, in particular, is a horrible hack. It would be nice if someone would think about a consistent, clean array system which can take advantage of Lisp arrays....
Imported from SourceForge on 2024-07-04 15:08:21 Created by willisbl on 2007-05-07 10:54:07 Original: https://sourceforge.net/p/maxima/bugs/1188
(%i1) use_fast_arrays : true$ (%i2) a[2] : 0$ (%i3) is(equal(a,b)); Maxima encountered a Lisp error: Error in MACSYMA-TOP-LEVEL [or a callee]: #<hash-table 1107bec4> is not of type LIST.
It's not just meqp with this bug: sign(a), assume(a < 0), a + 1, ... all give CL errors.