[Maxima-bugs] [ maxima-Bugs-1625792 ] Strange interaction of plot2d and remvalue.

[SourceForge.net <no...@so...>]

Bugs item #1625792, was opened at 2007-01-01 11:20
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104933&aid=1625792&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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Strange interaction of plot2d and remvalue.

Initial Comment:
Plot2d behaves very strangely. 

(%i1) g(s):=block([s__],s__:s,remvalue(s),s__)$
(%i2) g(2);
(%o2)                                  2
(%i3) plot2d(g,[t,1,2]);
Warning: Illegal `remvalue' attempt:
s
Warning: Illegal `remvalue' attempt:
s

etc...

The plot however is fine.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2007-01-01 11:21

Message:
Logged In: NO 

Follow up on the mailing list by Robert Dodier.

On 1/1/07, Michel Van den Bergh <mic...@uh...> wrote:

> But look at the example.  g(2) does *not* give a warning but g within
> plot2d does give warnings.

Michel, it turns out the strangeness is indeed within plot2d.

I've made 2 mistakes here.

(1) plot2d calls g in a nonstandard way (not via MFUNCALL).
So that's the origin of this bit of strangeness. For the record,
the bit to repair is COERCE-FLOAT-FUN in src/plot.lisp.

(2) When a Maxima function is called via MFUNCALL, the arguments
do indeed appear on the values list (therefore REMVALUE is happy).



best,
Robert 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104933&aid=1625792&group_id=4933