Timo Kuchheuser

I'm currently working on a patch that loads data/configuration from a json file. Depending on the values in the file set to specific attributes I want my patch to behave a certain way or give an error in case the values are inconsistent.

Please see my attached patch for an abstract example.

There are two combinations of values that should trigger two different behaviours in the patch and two combinations that should lead to some kind of error message.

Before I start patching together a lot of [if] and [gswitch] objects, I meant to ask what are some common patterns for complex decisions or which objects I could use to make my life easier.

comment

message

route

I'm currently working on a patch that loads data/configuration from a json file. Depending on the values in the file set to specific attributes I want my patch to behave a certain way or give an error in case the values are inconsistent.
Please see my attached patch for an abstract example.
There are two combinations of values that should trigger two different behaviours in the patch and two combinations that should lead to some kind of error message.
Before I start patching together a lot of [if] and [gswitch] objects, I meant to ask what are some common patterns for complex decisions or which objects I could use to make my life easier.

Hey all,
I'm currently working on a patch that loads data/configuration from a json file. Depending on the values in the file set to specifi

pattern-for-complex-decisions

it might be a matter of taste, but one strategy would be to make everything what is possible a bool (0 for falso, 1 for true ) and then perform logical, bitwise, comparative or arithmetic functions with them.

if true here && false there then blablabla 

to find out if both incoming states match the criteria.

so make yourself a little set of gates (auf deutsch: gatter - einfach mal nachschlagen, ist sehr erleuchtend) which perform such basic tasks far more effective and more generally than if then else constructions, and use them next time you need to do the same job.

using 0 and 1 for everything will also allow easily to perform list or database operations on these values , encode them into bigger numbers or symbols, and take less space for storage.


it might be a matter of taste, but one strategy would be to make everything what is possible a bool (0 for falso, 1 for true ) and then perform logical, bitwise, comparative or arithmetic functions with them.

for example instead of 

route true false 
if true here  && false there then blablabla 

you would just do 

+ 
== 2

to find out if both incoming states match the criteria.

so make yourself a little set of gates (auf deutsch: gatter - einfach mal nachschlagen, ist sehr erleuchtend) which perform such basic tasks far more effective and more generally than if then else constructions, and use them next time you need to do the same job.

using 0 and 1 for everything will also allow easily to perform list or database operations on these values , encode them into bigger numbers or symbols, and take less space for storage.



thank you for your answer. I will look into bitwise operations and gates.

That seems to be a possible solution for my patch.

P.S.: Hättest du Interesse an einer (natürlich bezahlten) Beratungsstunde per z.B. Skype?

Ich glaube, ich gehe mein Projekt ziemlich falsch an und brauche jemanden mit Erfahrung.

thank you for your answer. I will look into bitwise operations and gates.
That seems to be a possible solution for my patch.

P.S.: Hättest du Interesse an einer (natürlich bezahlten) Beratungsstunde per z.B. Skype?
Ich glaube, ich gehe mein Projekt ziemlich falsch an und brauche jemanden mit Erfahrung.

Pattern for complex decisions