1 #ifndef DataFormats_Common_traits_h
2 #define DataFormats_Common_traits_h
43 std::numeric_limits<typename key_traits<K>::key_type>
::max();
47 template <
class U,
class V>
54 template <
class U,
class V>
127 template <
class T,
class A>
139 template <
class T,
class A>
145 template <
class T,
class A>
151 template <
class T,
class A>
176 template <
class T,
class A>
188 template <
class T,
class A>
194 template <
class T,
class A>
200 template <
class T,
class A>
static const key_type value
static const key_type value
static const key_type value
std::pair< U, V > key_type
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
EventID const & max(EventID const &lh, EventID const &rh)