#include <vector>
#include <string>
#include <sstream>
#include <iterator>
#include "FWCore/Utilities/interface/Algorithms.h"
Go to the source code of this file.
◆ char_uint16
typedef unsigned char char_uint16[sizeof(uint16)] |
◆ char_uint32
typedef unsigned char char_uint32[sizeof(uint32)] |
◆ char_uint64
typedef unsigned char char_uint64[sizeof(uint64)] |
◆ Strings
typedef std::vector<std::string> Strings |
◆ uint16
◆ uint32
◆ uint64
typedef unsigned long long uint64 |
◆ uint8
typedef unsigned char uint8 |
◆ convert() [1/3]
◆ convert() [2/3]
◆ convert() [3/3]
Definition at line 54 of file MsgTools.h.
References findQualityFiles::v.
56 v[1] = (li >> 8) & 0xff;
57 v[2] = (li >> 16) & 0xff;
58 v[3] = (li >> 24) & 0xff;
59 v[4] = (li >> 32) & 0xff;
60 v[5] = (li >> 40) & 0xff;
61 v[6] = (li >> 48) & 0xff;
62 v[7] = (li >> 56) & 0xff;
◆ convert16()
◆ convert32()
Definition at line 28 of file MsgTools.h.
References a, b, HltBtagPostValidation_cff::c, ztail::d, and findQualityFiles::v.
Referenced by EventMsgView::droppedEventsCount(), InitMsgView::eventHeaderSize(), EventMsgView::EventMsgView(), HeaderView::HeaderView(), InitMsgView::InitMsgView(), EventMsgView::lumi(), EventMsgView::origDataSize(), EventMsgView::outModId(), edm::StreamerInputFile::readEventMessage(), InitMsgBuilder::run(), InitMsgView::run(), and EventMsgView::run().
30 unsigned int a =
v[0],
b =
v[1],
c =
v[2],
d =
v[3];
31 a |= (
b << 8) | (
c << 16) | (
d << 24);
◆ convert64()
Definition at line 20 of file MsgTools.h.
References a, b, HltBtagPostValidation_cff::c, ztail::d, MillePedeFileConverter_cfg::e, f, g, h, and findQualityFiles::v.
Referenced by EventMsgView::event(), and edm::StreamerInputFile::readEventMessage().
22 unsigned long long a =
v[0],
b =
v[1],
c =
v[2],
d =
v[3];
23 unsigned long long e =
v[4],
f =
v[5],
g =
v[6],
h =
v[7];
24 a |= (
b << 8) | (
c << 16) | (
d << 24) | (
e << 32) | (
f << 40) | (
g << 48) | (
h << 56);
The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Services can connect to the signals distributed by the ActivityRegistry in order to monitor the activity of the application Each possible callback has some defined which we here list in angle e g
The Signals That Services Can Subscribe To This is based on ActivityRegistry h
Helper function to determine trigger accepts.