Menu
▾
▴
#3872 maxima matches to a parenthesis within a comment while everything in a comment should be ignored!
build_info(version="branch_5_44_base_231_g5c411f69f",timestamp="2021-01-12 23:51:42",
host="x86_64-w64-mingw32",
lisp_name="SBCL",
lisp_version="2.0.0",
maxima_userdir="C:/Users/zmth1/maxima",
maxima_tempdir="C:/Users/zmth1/AppData/Local/Temp",
maxima_objdir="C:/Users/zmth1/maxima/binary/branch_5_44_base_231_g5c411f69f/sbcl/2_0_0",
maxima_frontend="wxMaxima",
maxima_frontend_version="20.12.2-DevelopmentSnapshot_MSW_OpenMP201511+Locks")
(kill(a,b,c,F,n) ,fl:true,F(n,k):=(n+k)!*(b+k)!*(c-n-1)!*(c-b-1)!/(c+k)!/(n-1)!/(c-n-b-1)!/(k+1)!/(b-1)!
,t:ratsimp( -((n+k+1)*(-n+c-b-1)-n*(-n+c-1)) -(n+k+1)*(b+k+1)+(k+1)*(k+c)),if t#0 then(fl:false,disp(["t",t]))
,declare(n,integer),assume(n<0),for n:0 thru -3 step -1 do for b:-8/4 thru 16/4 do for c:-4thru 4
do if not integerp(c-b) or c>b then
/*
(t:0,for k:-1 thru -1-n do(kt:float(prod(c-n-1-i,i,0,-n-2-k)*prod(b+k-i,i,0,k)/prod(c-n-b-1-i,i,0,-n-1)/prod(k+1-i,i,0,k-1)
*prod(n+k-i,i,0,k)),t:t+kt,if abs(kt)>99999911 then disp(["n",n,"b",b,"c",float(c),"float(b-c)",float(b-c),"k",k,"kt",kt]))
*/
(t:float(sum(prod(c-n-1-i,i,0,-n-2-k)*prod(b+k-i,i,0,k)/prod(c-n-b-1-i,i,0,-n-1)/prod(k+1-i,i,0,k-1)
*prod(n+k-i,i,0,k),k,-1,-n-1)) ,if abs(t-1)>1e-7 then(fl:false,disp(["t#1,t"=t]))), fl )
Hover over the last ending parenthesis in the code routine just above that is after the fl and it shows the matching parenthesis to be one within the /....../ that is within the comment , all of which should be ignored but maxima DOESN'T do that ignoring. It should have matched it to the very first '( ' in the routine the one before kill(.... but maxima DOES NOT do that correct thing but CONFUSINGLY matches it to a paren. within the comment - in fact the first one in the comment !
Since this is a bug in the wxMaxima front end, it should be reported to the wxMaxima issue tracker (https://github.com/wxMaxima-developers/wxmaxima/issues). Closing this ticket as "won't fix" since it is not a bug in Maxima itself.
as if I nor anyone else knows anything about wxMaxima issue tracker means nor the difference between that and regular bugs
Google [wxMaxima issue tracker].
I Believe the user meant that sometimes it is hard to find out which project to report bugs to. Actually even I sometimes am not sure which of the two projects a bug is in (or, sometimes, which project it is better to resolve it in) and not everyone knows that in open source most of the times the GUI and the program that does the actual work are separate projects. Additionally users see that the same developer might help them regardless which project they report the project in and not everyone thinks (Or even knows) about the possibility to re-test things in plain maxima and isn't too scared of the console.
My 5 cents: Sometimes if you are kind to a scared user you'll get helpful bug reports, someone who recruits future devs or even a future developer in the long run. And sometimes an obvious troll turns out just to be from a country with different ways of reporting bugs.
On the other hand: we once fed a troll instead, for a few days And I rarely have colleagues that just won't turn helpful. You never know...
Robert very helpfully identified this as a bug in the wxMaxima front end, and gave a link to the issue tracker (which is also easy to find with Google), without implying that the user should have known that the problem was in wxMaxima or otherwise criticizing the user.
I think we've been quite kind to this user, even though he has a history of aggressive and insulting language in problem reports, e.g., "how ignorant can u get" (https://sourceforge.net/p/maxima/bugs/3874/); "get bogus irrelevant error message" (https://sourceforge.net/p/maxima/bugs/3899/); "Did you even look at the output" (https://sourceforge.net/p/maxima/bugs/3975/). In these and other cases, the problem has often been user error, but we went out of our way to provide constructive suggestions.
Last edit: Stavros Macrakis 2022-05-30
Ok... ...I remember these messages - and now I do understand your answer. But the bug report Itself was important, as it showed me a nasty bug...
I believe I found a fix to that in wxMaxima that will be in the next wxMaxima version.