Browse Source

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
master
Dave Parker 15 years ago
parent
commit
ac4cefbb45
  1. 4
      prism/src/parser/ast/Filter.java

4
prism/src/parser/ast/Filter.java

@ -36,7 +36,7 @@ public class Filter extends ASTElement
{ {
private Expression expr = null; private Expression expr = null;
// Either "min" or "max", or neither or both. // 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 minReq = false;
private boolean maxReq = false; private boolean maxReq = false;
@ -57,13 +57,11 @@ public class Filter extends ASTElement
public void setMinRequested(boolean b) public void setMinRequested(boolean b)
{ {
minReq = b; minReq = b;
maxReq = !b;
} }
public void setMaxRequested(boolean b) public void setMaxRequested(boolean b)
{ {
maxReq = b; maxReq = b;
minReq = !b;
} }
// Get methods // Get methods

Loading…
Cancel
Save