On 4/11/2024 3:26 AM, Isaac Keslassy wrote: > Your discussion is getting far from gnubg bugs, and > causing people to unsubscribe the list. Any chance > you can take it private? Thanks.
You must be one of the owner of this forum? Since my intention is not merely to disturb comfortably numb minds but to stimulate open minds, (with at least Ian being one), I will gladly oblige. However, I don't understand why our discussion about fundamental flaws in GnuBG would be appropriate here. Perhaps you all consider GnuBG near perfect with only paint chips on the wall and don't want to hear about the cracks in the foundation? No problem. Here is a tiny little bug that I hope you will be able to help me with: Since I have been running experiments using my Python scripts that I have shared on my web page, every now and then I get the "unknown cube decision" error when I call the "gnubg.cfevaluate()" function. It's coming from line 3172 of "eval.c" at this link: https://cvs.savannah.gnu.org/viewvc/gnubg/gnubg/eval.c?revision=1.498&view=markup In lines 3131-3172, there are 20 possible cases for cube decisions. They don't seem to be in the same order as "int recommendation" returned by the function since the value returned for the above error is "15". Checking for the error after the fact is of no use and all I can do is to restart the script. I'm completely baffled by this pathetic error message that seems to be a tracing remnant of a tiny little bug that the GnuBG team has never been able to figure out and fix. :( Would you be kind enough to look into this if you deem it an appropriate subject for this forum? Thanks. MK