|
From: David S. <tom...@us...> - 2026-06-02 07:03:53
|
- **status**: open --> maybe-fixed - **Comment**: I pushed commit [46cd19], which restores some numerical inferences, detects lots of inconsistent type declarations and greatly simplifies `decl-realp`. The issue "real vs. complex" is not resolved yet. --- **[bugs:#4749] Declaring a symbol both real and complex or real and imaginary** **Status:** maybe-fixed **Group:** None **Labels:** declare rectform featurep csign **Created:** Mon Jun 01, 2026 07:19 AM UTC by David Scherfgen **Last Updated:** Mon Jun 01, 2026 10:40 PM UTC **Owner:** nobody Maxima allows declaring a symbol both `real` and `complex` and even both `real` and `imaginary`. I think that in the second case, it should at least issue a warning, if not an error. For the first case, where a symbol is declared both `real` and `complex`, Maxima behaves differently across `csign`, `rectform` and `featurep`: ~~~ (%i1) declare(x, real, x, complex); (%o1) done (%i2) csign(x); (%o2) complex (%i3) rectform(x); (%o3) x (%i4) featurep(x, real); (%o4) true (%i5) featurep(x, complex); (%o5) true ~~~ These functions all have a different concept ... --- Sent from sourceforge.net because max...@li... is subscribed to https://sourceforge.net/p/maxima/bugs/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/maxima/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |