Matteo Cafasso

The `plugins` folder was initially intended as a place where to provide some reference implementation of SEE plugins. It ended up in the package by mistake. Nevertheless, I think it...

CLIPS does not implement exceptions. Therefore, it won't raise any `CLIPSError` when invoking the `run` function. The `run` function always returns the amount of fired rules. The reason why you...

What OS are you running the code on? When you mention kernel, I guess you mean the Python interpreter? Are you using plain Python or iPython?

I can confirm the issue. Nevertheless, the problem lies within the CLIPS engine itself and not CLIPSPy. Hence, it will take some time to get it fixed as it's out...

Issue reported to upstream project: https://sourceforge.net/p/clipsrules/tickets/69/

Usually that error appears when you are importing the module from the wrong path. If you used: ```bash PYTHON=python3 sudo make install ``` It should have installed the package via...

Hi @bigbigbanana, the original Nitro project is not maintained anymore. The results you see are the raw registry values for each syscall and their translation is a big effort we...

Regarding the use of a simple array vs a hash table you have quite a valid point. Yet I realized a corner case to be considered which is affecting both...

I run in a problem which I don't know if it is a bug or a misuse of mine. If I open a header which is included by a .cpp...

I think the culprit might lie in the cache being full. Currently, the `x-cache-size` parameter controls the maximum amount of members within the cache. When the cache overflows, an item...