Re: Evaluate complex conditions

["James W. Kilgore" <eMail@xxxxxxxxxxxxxxxxxxx>]

Terry,

I'm in Richard's camp with stack machines.  Pushing and popping a stack
is similar to doing a cost roll-up in a bill of materials where you keep
nesting (pushing) until you reach the bottom the then work your way back
up (pop).

BTW, Years ago, about 20 or so, there was an attempt at natural language
queries.  Sort of like: Give me a list of all the registered voters in
New Hampshire and Vermont.

The system would return nothing.  You can't be registered in New
Hampshire -and- Vermont.

It was discovered that too few people know how to phrase a proper
question.

Terry Grider wrote:
> 
> You're on the right track Booth except I'm not brave enough to allow TOTAL
> english syntax.  I was just hoping to be able to provide simple = , not=, <, 
>>,
> not>, not<  type compares between field names and literal values, which I have
> coded for and have working at this point, but only with simple single level
> conditions connected by a series of either 'ANDs' or 'ORs'.  Naturally, first
> time a user wanted to try out my little query tool, they needed support for
> complex, multi-level conditions.  Isn't that always the way it goes!
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---