Conditional Statements/Boolean Logic as Array

[RedBassett]

Here's a question I can't seem to figure out.

How would one go about breaking down the structure of nested conditional statements into an array (for storage and handeling between lower-level code)?

For example, you could break down a single condition easily:
if x == y then… => ['x', '==', 'y']

But what about:
if x == y and z > 0, or if (x == y and z > 0) or x == z.

This gives us up to three comparisons:
[['x', '==', 'y'], ['z', '>', '0'], ['x', '==', 'z']

But no way to add the Boolean logic parts.

[coolcoolcool]

What kind of low level code? Application could change how the problem is tackled.

I've never had a reason to break down boolean logic into an array before.

[RedBassett]

Not low-level, simply lower-level. I am attempting to build an interface where statements are put into an application that will process them, without having to create a syntax for strings to then parse. Essentially I want a way to put the above statements into a function as a parmeter that the function can evaluate.

[coolcoolcool]

Seems counter intuitive to me, but I'm probably not understanding what you're doing.

Why not use a stack and a custom postfix notation that allows for ands, negates, and ors? That's a pretty common problem and there's pseudo code for it already tailor made all over the internet.

[RedBassett]

May 10, 2012 18:52:54 GMT -8 coolcoolcool said:

Seems counter intuitive to me, but I'm probably not understanding what you're doing.

Why not use a stack and a custom postfix notation that allows for ands, negates, and ors? That's a pretty common problem and there's pseudo code for it already tailor made all over the internet.

I'm thinking I may use a custom pseudo-code for it, but I was trying to create something that did not require passing strings to the function.

[Charles Stover]

Why not:
[['x', '==', 'y'], '&&', ['z', '>', '0'], '&&', ['x', '==', 'z']]

If the item is an array ([x, ==, z]), then evaluate it as a comparison; if it's a string (&& or ||), then evaluate it as an operator.

Really, though, I don't see the benefit to this. It brings problems with things like (($x == 0 || $y == 1) && $z == 2)

You should just send the entire string to evaluate.

[RedBassett]

May 11, 2012 10:20:11 GMT -8 Charles Stover said:

Why not:
[['x', '==', 'y'], '&&', ['z', '>', '0'], '&&', ['x', '==', 'z']]

If the item is an array ([x, ==, z]), then evaluate it as a comparison; if it's a string (&& or ||), then evaluate it as an operator.

Really, though, I don't see the benefit to this. It brings problems with things like (($x == 0 || $y == 1) && $z == 2)

You should just send the entire string to evaluate.

You would nest by replacing one of the comparisons with an array similar to that one?

[coolcoolcool]

I'm still saying a single array of postfix operators and values would be best.