noxdafox

Segfault with IMPutSlot of subclass instance

Yes, if you intend to share an environment across multiple threads, you shall protect it from mutual access of its API. From the 1.2 Threads and Concurrency chapter of the Advanced Programming Guidelines: Each environment can have at most one thread of execution. The CLIPS internal data structures can become corrupted if two CLIPS API calls are executing at the same time for a single environment. For example, you can’t have one thread executing rules and another thread asserting facts for the same...

Are you asserting facts concurrently from different threads? CLIPS does not support multithreading on single environments. Il giorno lun 13 set 2021 alle ore 07:11 Faraz Zabihian farazex@users.sourceforge.net ha scritto: That "clock =" is meant to be " tick". My bad embedded clips, Assertstring and segmentation fault https://sourceforge.net/p/clipsrules/discussion/776945/thread/7887a94397/?limit=25#8927 Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/clipsrules/discussion/776945/...

CLIPSPy 1.0.0 has been released. This version is based on CLIPS 6.40. The APIs have been refactored based on the learnings with CLIPS 6.30 and to better reflect the changes in the C ones. Test coverage has also been increased. Python 2 support has been dropped and the minimum supported Python version is now 3.6. iCLIPS as well has been ported to the new library version. clipspy: https://pypi.org/project/clipspy/ iCLIPS: https://pypi.org/project/iCLIPS/ Thanks @garyriley for releasing CLIPS 6.40!

Feature request: defconstruct docstrings

Thanks! I already updated the Python bindings Makefile to use the new release.

Release CLIPS 6.32

Hello, I would ask you to open a separate issue on GitHub as these seem bugs at first sight. Let's keep this forum for more generic discussions.