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 Gerta Fareta on 3/13/2026 11:49 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

    Gerta Fareta (Friday, March 13, 2026 11:49 AM) #

Welcome everyone! I saw a video from a creator based in Edinburgh who was showing off their winnings on a new platform. I’d been feeling quite unlucky lately and was nearly ready to stop playing for good. I checked out wishwin and spent my afternoon on the slots online. To my surprise, I landed a win that was ten times my initial stake. I also enjoyed the online casino bets poker section. It was a great result that made me feel much better.

    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.