You can use RETE rule engines which are better than Prolog at handling hundreds of rules.
You get out of that imperative trap and you delegate control to the rule compiler to decide
the rule evaluation order.
The runtime takes care of executing your rules until the output stops changing.
I wrote a couple of apps using this and it's a very good approch when you know that your system
will have to adapt to future changes. Rules are independent and it's easier to add/remove individual
decoupled rules than reworking a 💩 pile of code all intertwined.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You can use RETE rule engines which are better than Prolog at handling hundreds of rules.
You get out of that imperative trap and you delegate control to the rule compiler to decide
the rule evaluation order.
The runtime takes care of executing your rules until the output stops changing.
I wrote a couple of apps using this and it's a very good approch when you know that your system
will have to adapt to future changes. Rules are independent and it's easier to add/remove individual
decoupled rules than reworking a 💩 pile of code all intertwined.