Bug SS-4622
1 vote
vote

[Maxima] Assign() fails if it is part of a definition
Created by Martin Kraska on 11/3/2019 3:50 PM Last Updated by Martin Kraska on 6/7/2023 12:53 AM
%
 (hrs)
Logged: 0   (hrs)

 Description

EDIT 2023: The correct behaviour is obtained if the line operator is used. Objective of bug fix: Restore this behaviour but without use of line operator.

 

Due to API changes, Assign() is partially broken. It just evaluates it's arguments but is not evaluated itself.

An option might be to integrate the replacement into the pre-processing. This also might work for Solve() (integrate the Maxima function call into preprocessing)!

But maybe, the preprocessing isn't under control of the plugin...
Skip Navigation Links

    Martin Kraska (Wednesday, June 7, 2023 12:48 AM) #

The problem can be described more specifically. 

The standard way without tricks. Problem is that the result of Assign() can't be stored to another variable.

 

Version with eval(), storage is possible but eval looks weird at display of L and enforces unwanted conversion to non-exact representation

Version with line-block: This is the best way, because behaviour exactly matches the design intent.