Re: [henshin-dev] Using EOperations as attribute constraints

[Elie Richa <richa@xxxxxxxxxxx>]

Hi Christian,

Thank you for your answer. Another slightly related question below.

> My practical use of this is a higher-order transformation which transforms
> Henshin rules :) I'd like to create a rule which simplifies Formulas when
> the EOperations isTrue() or isFalse() evaluate to true.

I notice the following in NestedConditionImpl.isFalse()

    public boolean isFalse() {
        // There seems to be no situation where we can definitely say it is always false.
        return false;
    }

However, in the case where the nested condition has a formula that
isFalse(), doesn't it mean that the nested condition always evaluates to
false?

So basically is the following implementation of
NestedConditionImpl.isFalse() correct?

    public boolean isFalse() {
        Formula formula = conclusion.getFormula();
        if (formula != null && formula.isFalse()) {
            return true;
        } else {
            return false;
        }
    }

Thanks.

--
Elie