From ac4cefbb45eac001a7e3ff2a07143f6e537d27d3 Mon Sep 17 00:00:00 2001 From: Dave Parker Date: Tue, 14 Dec 2010 23:11:29 +0000 Subject: [PATCH] Fix behaviour of old-style {min}{max} filters. git-svn-id: https://www.prismmodelchecker.org/svn/prism/prism/trunk@2330 bbc10eb1-c90d-0410-af57-cb519fbb1720 --- prism/src/parser/ast/Filter.java | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/prism/src/parser/ast/Filter.java b/prism/src/parser/ast/Filter.java index aa52f53f..50811124 100644 --- a/prism/src/parser/ast/Filter.java +++ b/prism/src/parser/ast/Filter.java @@ -36,7 +36,7 @@ public class Filter extends ASTElement { private Expression expr = null; // Either "min" or "max", or neither or both. - // In the latter case, this means "range" + // In the latter two cases, this means "range" private boolean minReq = false; private boolean maxReq = false; @@ -57,13 +57,11 @@ public class Filter extends ASTElement public void setMinRequested(boolean b) { minReq = b; - maxReq = !b; } public void setMaxRequested(boolean b) { maxReq = b; - minReq = !b; } // Get methods