Jon S Berndt writes:
< >
> <COMPONENT NAME="{name}" TYPE="SWITCH">
> <TEST LOGIC="{AND|OR|DEFAULT}"
> VALUE="{property|value}">
> {property} {conditional} {property|value}
> ...
> </TEST>
> <TEST LOGIC="{AND|OR|DEFAULT}"
> VALUE="{property|value}">
> {property} {conditional} {property|value}
> ...
> </TEST>
> ...
> </COMPONENT>
>
> This is a request for developer community comment :-)
> For an example:
< >
> <COMPONENT NAME="PITCH_OVERRIDE" TYPE="SWITCH">
> <TEST LOGIC="DEFAULT" VALUE="1.0">
> </TEST>
> <TEST LOGIC="AND" VALUE="4.0">
> panel/pitch_override EQ true
> </TEST>
> </COMPONENT>
Jon
It appears to me that you are *real close* to reinventing
the 'rule based' progamming paradigm.
There should be some 'CLIPS' experts running around the same
'hangars' that you frequent that might have some *good* input
Cheers
Norman
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
