CMS 3D CMS Logo

IterWithDict.cc
Go to the documentation of this file.
2 #include <cassert>
3 
4 namespace edm {
5 
7  if (atEnd_) {
8  return;
9  }
10  TObject* obj = iter_.Next();
11  if (obj == nullptr) {
12  atEnd_ = true;
13  }
14  }
15 
16  TIter const& IterWithDictBase::iter() const { return iter_; }
17 
19  // This ctor is used by the framework for the end of a range,
20  // or for any type that does not have a TClass.
21  // An iterator constructed by this ctor must not be used
22  // as the left hand argument of operator!=().
23  }
24 
26  // With a TIter, you must call Next() once to point to the first element.
27  TObject* obj = iter_.Next();
28  if (obj == nullptr) {
29  atEnd_ = true;
30  }
31  }
32 
34  // The special cases are needed because TIter::operator!=()
35  // dereferences a null pointer (i.e. segfaults) if the left hand TIter
36  // was constucted with a nullptr argument (the first constructor above).
37  if (atEnd_ != rhs.atEnd_) {
38  // one iterator at end, but not both
39  return true;
40  }
41  if (atEnd_) {
42  // both iterators at end
43  return false;
44  }
45  // neither iterator at end
46  return iter_ != rhs.iter_;
47  }
48 
49 } // namespace edm
bool operator!=(IterWithDictBase const &) const
Definition: IterWithDict.cc:33
#define nullptr
HLT enums.
TIter const & iter() const
Definition: IterWithDict.cc:16
How EventSelector::AcceptEvent() decides whether to accept an event for output otherwise it is excluding the probing of A single or multiple positive and the trigger will pass if any such matching triggers are PASS or EXCEPTION[A criterion thatmatches no triggers at all is detected and causes a throw.] A single negative with an expectation of appropriate bit checking in the decision and the trigger will pass if any such matching triggers are FAIL or EXCEPTION A wildcarded negative criterion that matches more than one trigger in the trigger list("!*","!HLTx*"if it matches 2 triggers or more) will accept the event if all the matching triggers are FAIL.It will reject the event if any of the triggers are PASS or EXCEPTION(this matches the behavior of"!*"before the partial wildcard feature was incorporated).Triggers which are in the READY state are completely ignored.(READY should never be returned since the trigger paths have been run