http://www.mapleprimes.com/posts/40988-Evalhf-And-Module-Export-Question en-us 2026 Maplesoft, A Division of Waterloo Maple Inc. Maplesoft Document System Tue, 09 Jun 2026 19:03:34 GMT Tue, 09 Jun 2026 19:03:34 GMT The latest comments added to the Post, evalhf and module export question http://www.mapleprimes.com/images/mapleprimeswhite.jpg http://www.mapleprimes.com/posts/40988-Evalhf-And-Module-Export-Question http://www.mapleprimes.com/posts/40988-Evalhf-And-Module-Export-Question?ref=Feed:MaplePrimes:evalhf and module export question:Comments#comment76041 Look at the following: <pre>&gt; ToInert(p:-sin); _Inert_ASSIGNEDLOCALNAME("sin", "PROC", 143973196, _Inert_ATTRIBUTE( _Inert_NAME("protected", _Inert_ATTRIBUTE(_Inert_NAME("protected"))))) </pre> which mostly says that p:-sin looks like a (local) name 'sin'. And evalhf does its dispatch based <strong>solely</strong> on the name of the function. Whether this is right or wrong is another matter, but it is in many ways ``expected''. The latest comments added to the Post, evalhf and module export question 76041 Fri, 10 Aug 2007 17:23:52 Z JacquesC JacquesC http://www.mapleprimes.com/posts/40988-Evalhf-And-Module-Export-Question?ref=Feed:MaplePrimes:evalhf and module export question:Comments#comment85169 While I thank you for the response, Jacques, I'll say that it sounds more like a description of the mechanism that might be used than a rationale for the behaviour. Which new user wouldn't get caught by this? Which expert would guess the (new to Maple 11) behaviour? It's quite a fumble. In Maple 10, it did not work like that. Maple would issue an error saying that p:-sin was unknown to it. Eg, "Error, unable to evaluate function `p:-sin` in evalhf". If Maple 10 can figure out that p:-sin is unknown to it, then Maple 11 should be able to figure out not to dispatch to the global :-sin wherever the code contains the module member p:-sin. It's a strange behaviour. Did I miss where it's documented, I wonder? Would it affect all function names mentioned in the help-page ?evalhf,fcnlist ? acer The latest comments added to the Post, evalhf and module export question 85169 Fri, 10 Aug 2007 18:31:50 Z acer acer http://www.mapleprimes.com/posts/40988-Evalhf-And-Module-Export-Question?ref=Feed:MaplePrimes:evalhf and module export question:Comments#comment91769 My description was indeed 'operational' rather than a justification. It is indeed strange that this started ``working'' in Maple 11, it seems like a regression rather than an improvement! I cannot really think of a rationale for doing this (other than ``it can be done''). Hopefully we'll get an official answer on this one. But, just to be sure, you should probably file this as a bug with support@maplesoft.com. The latest comments added to the Post, evalhf and module export question 91769 Fri, 10 Aug 2007 19:52:00 Z JacquesC JacquesC http://www.mapleprimes.com/posts/40988-Evalhf-And-Module-Export-Question?ref=Feed:MaplePrimes:evalhf and module export question:Comments#comment85167 This confused me, because I thought the problem in the <a href="http://www.mapleprimes.com/forum/invalid-object-in-mesh">"invalid object in MESH" thread</a> was that evalhf can't handle RealDomain:-sin, and here evalhf treats p:-sin the same as sin. The distinction, I think, is that in the plot3d example the sin function gets called inside a "wrapper" function that is sent to evalhf. Thus: <pre> > p := module() option package; export sin; sin:=proc(x) x; end proc; end module: with(p): q:= proc(x) sin(x) end proc; sin(1); </pre> 1 <pre> > evalhf(sin(1)); </pre> .841470984807896505 <pre> > evalhf(q(1)); </pre> Error, unable to evaluate function `p:-sin` in evalhf The latest comments added to the Post, evalhf and module export question 85167 Sat, 11 Aug 2007 00:03:12 Z Robert Israel Robert Israel http://www.mapleprimes.com/posts/40988-Evalhf-And-Module-Export-Question?ref=Feed:MaplePrimes:evalhf and module export question:Comments#comment91770 In other words, even if the current very partial handling of module exports is by-design, it is quite fragile. By all accounts, it seems that the Maple 10 behaviour was definitely preferable. Hopefully this regression will be fixed in 12. The latest comments added to the Post, evalhf and module export question 91770 Sat, 11 Aug 2007 01:03:07 Z JacquesC JacquesC http://www.mapleprimes.com/posts/40988-Evalhf-And-Module-Export-Question?ref=Feed:MaplePrimes:evalhf and module export question:Comments#comment91779 > f := module() export g; g:=proc(x) x; end proc; end module: > evalhf(f:-g(1.1)); 1.10000000000000008 > evalhf(proc() f:-g(1.1); end proc()); Error, unable to evaluate function `f:-g` in evalhf > proc() f:-g(1.1); end proc(); 1.1 > g:=proc(x) x; end proc: > evalhf(proc() g(1.1); end proc()); 1.10000000000000008 There are two problems. The first was that top-level global sin was used instead of the module export foo:-sin. The second is that, more generally, evalhf can find and use module exports when outside a procedure but not when within procedures. acer The latest comments added to the Post, evalhf and module export question 91779 Fri, 17 Aug 2007 20:03:01 Z acer acer