CLHEP VERSION Reference Documentation
   
CLHEP Home Page     CLHEP Documentation     CLHEP Bug Reports

Functions | Variables
mechanics_ZMx.txt File Reference
#include "Exceptions/ZMexception.h"
#include "Exceptions/ZMthrow.h"
#include "Exceptions/ZMexHandler.h"
#include "Exceptions/ZMexLogger.h"
#include "Exceptions/ZMerrno.h"

Functions

Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix ZMex (or, in the case of the preprocessor, "ZMEX") in order to help avoid namespace pollution. For example
 
Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix we use ZMexception as the name of the class from which all other exception classes are (directly or indirectly) derived. Additionally
 
any previously defined ZMexception may be used as the parent Oops is the exception s name as it is to appear in the log Such a quoted exception name string should for clarity be closely related to the actual name but as shown here might omit some package identifying baggage ExcTest is the logged message prefix (normally indicating the package, facility, or program giving rise to the message). 5) ZMexWARNING is the default severity level of ZMxOops.(See below for a complete list of possible severity levels and the intended significance of each.) 3. Constructing/throwing an instance of the new exception class --------------------------------------------------------------- This Exceptions package provides a facility
 
any previously defined ZMexception may be used as the parent Oops is the exception s name as it is to appear in the log Such a quoted exception name string should for clarity be closely related to the actual name but as shown here might omit some package identifying baggage ExcTest is the logged message ZMthrow ()
 
Ouch may be arbitrary text to be associated with this particular occurrence (exception instance). The text will be logged
 
logging can probably cease after (say) 50 of the same warnings. ZMexERROR We encountered something such that
 
logging can probably cease although we can make it safe to continue running (e.g., by supplying a default value instead of a value we can 't for some reason calculate)
 
ought always be logged (but may be sensible, if hundreds of the same error are intentionally ignored, to stop logging each one). ZMexSEVERE The action you intended will almost certainly have a seriously flawed outcome and we doubt that either we or you can make it safe to continue if you ignore this
 
and for determining whether the exception instance can safely be ignored by the user code The Exceptions package includes a number of pre defined handlers (listed below)
 
and for determining whether the exception instance can safely be ignored by the user code The Exceptions package includes a number of pre defined implementing several commonly wanted behaviors Each exception class is associated with a handler to be applied to all ZMthrow n instances of that class By default this handler implements the behavior known as ZMexHandleViaParent ()
 
The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw ZMexIgnoreAlways () the ZMthrow 'n exception instance will be handled
 
The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw but will have no further affect on subsequent control flow ZMexThrowErrors () the ZMthrow 'n exception instance will
 
The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw but will have no further affect on subsequent control flow after be thrown if its severity is ZMexERROR or but be ignored if of a lesser severity the intended (direct or indirect) ancestor class of all other exception classes. ZMexIgnoreNextN(n) the next n occurrences of a ZMthrow 'n instance of this class will be ignored after handling
 
it is not responsible for determining or formatting any message The Exceptions package includes a few pre defined loggers (listed below)
 
it is not responsible for determining or formatting any message The Exceptions package includes a few pre defined implementing several commonly wanted logging behaviors Each exception class is associated with a logger to be applied to all ZMthrow n instances of that class By default this logger implements the behavior known as ZMexLogViaParent ()
 
The given behavior will apply to any exceptions ZMthrow n after the logger has been provided the handler invokes the logger Available loggers Here is a list of the standard loggers that are defined via the Exceptions package Each is accompanied by a brief description of its the intended (direct or indirect) ancestor class of all other exception classes. ZMexLogTwice(ostream &Dest1
 
user code seldom needs to call this function directly ZMerrno count () Return the(integer) number of ZMthrow 'n exceptions ever recorded via ZMerrno.write()
 
user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno size () Return the(integer) number of ZMthrow 'n exceptions currently recorded. 5) ZMerrno.clear() Set an internal counter to zero. This counter is available(see next function) to user code to track ZMthrow 'n exceptions that have occurred during any arbitrary time interval. 6) ZMerrno.countSinceCleared() Return the(integer) number of ZMthrow 'n exceptions that have been recorded via ZMerrno.write()
 
user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last cleared (see previous function). 7) ZMerrno.name(unsigned int k=0) Return the name(as logged) of the latest-but-k exception currently recorded via ZMerrno. Thus
 
user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno name () gives the(string) name of the latest recorded exception
 
user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno name (1) gives the name of the exception recorded immediately before the last one. 8) ZMerrno.get(unsigned int k=0) Return a(const pointer to) the latest-but-k exception currently recorded via ZMerrno. Thus
 
user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno ZMerrno get () gives a(const pointer to) the latest recorded exception
 
user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno ZMerrno while ZMerrno get (1) gives the corresponding pointer to the exception recorded immediately before the last one. This may be useful to peruse the exception 's message text
 
user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno ZMerrno while ZMerrno to note the handler and logger used when the exception was ZMthrow n etc The resulting pointer should generally be checked against in case ZMerrno does not go back as far as requested ZMerrno erase () Remove the most recently-recorded exception. This can be useful if
 

Variables

Introduction to the Use of Zoom Exceptions W E Brown
 
Introduction to the Use of Zoom Exceptions W E Oct
 
Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix we use ZMexception as the name of the class from which all other exception classes all ZOOM generated ZMexception classes will use at least ZMx as their name prefix More typically
 
Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix we use ZMexception as the name of the class from which all other exception classes all ZOOM generated ZMexception classes will use at least ZMx as their name prefix More to avoid internal name clashes
 
Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix we use ZMexception as the name of the class from which all other exception classes all ZOOM generated ZMexception classes will use at least ZMx as their name prefix More to avoid internal name the names start with a short string identifying the package
 
Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix we use ZMexception as the name of the class from which all other exception classes all ZOOM generated ZMexception classes will use at least ZMx as their name prefix More to avoid internal name the names start with a short string identifying the e g ZMxHep for HepTuple
 
In the example above
 
it is important to be consistent ZMexception is the name of the parent exception class of ZMxOops
 
 Here
 
Ouch may be arbitrary text to be associated with this particular as described below Resulting log message Assuming that the ExcTest program has been compiled with appropriate compiler switches that enable use of exceptions
 
Ouch may be arbitrary text to be associated with this particular as described below Resulting log message Assuming that the ExcTest program has been compiled with appropriate compiler switches that enable use of the logged message resulting from the above ZMthrow(...) example will be W it is considered a Warning
 
Oops it is classified as an Oops occurrence
 
Thu timestamp
 
exctest1 cc this occurrence arose from this associated compilation unit
 
always safe to ignore
 
typically not worth logging since it s probably just a temporary placeholder ZMexINFO In the normal course of events
 
typically not worth logging since it s probably just a temporary placeholder ZMexINFO In the normal course of here is news worth logging
 
often useful for progress reporting and for debugging purposes ZMexWARNING Something unusual has happened
 
often useful for progress reporting and for debugging purposes ZMexWARNING Something unusual has but we have a quite reasonable action to take
 
it s generally safe to ignore the warning because you ll probably get just about the result you intended
 
logging can probably cease although we can make it safe to continue you probably won t get the result you expected unless you handle this yourself
 
ought always be logged ZMexFATAL We can make no representations as to the state of any part of the software
 
ought always be logged ZMexFATAL We can make no representations as to the state of any part of the even of software parts not obviously associated with the failed intended action and even if you try to handle the problem
 
ought always be logged and essentially never be ignored ZMexPROBLEM The software has reached a logically impossible internal state
 
must always be logged and never be ignored
 
if encountered
 
if should always be reported to the software s developers and or maintainers Using handlers In the Exceptions a handler is the term for an instance of a class that processes a ZMthrow n exception A handler is responsible for having the exception instance logged
 
 Alternatively
 
The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its behavior
 
The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after handling
 
The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw but will have no further affect on subsequent control flow after be thrown if its severity is ZMexERROR or higher
 
The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw but will have no further affect on subsequent control flow after be thrown if its severity is ZMexERROR or but be ignored if of a lesser severity Note
 
subsequent instances will be thrown after handling a logger is the term for an instance of a class that records to a designated destination a ZMthrow n exception A logger is responsible only for routing the message associated with an exception instance
 
The given behavior will apply to any exceptions ZMthrow n after the logger has been established
 
The given behavior will apply to any exceptions ZMthrow n after the logger has been provided the handler invokes the logger Available loggers Here is a list of the standard loggers that are defined via the Exceptions package Each is accompanied by a brief description of its the ostream & Dest2
 
 thus
 
user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still recorded
 
user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno ZMerrno while ZMerrno to note the handler and logger used when the exception was ZMthrow n etc The resulting pointer should generally be checked against in case ZMerrno does not go back as far as requested ZMerrno for example
 
user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno ZMerrno while ZMerrno to note the handler and logger used when the exception was ZMthrow n etc The resulting pointer should generally be checked against in case ZMerrno does not go back as far as requested ZMerrno for there is a loop of known ignorable all nonetheless duly recorded by the handler These exceptions can be more interesting
 

Function Documentation

◆ after()

logging can probably cease after ( say  )

◆ are()

Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix we use ZMexception as the name of the class from which all other exception classes are ( directly or  indirectly)

◆ cleared()

user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last cleared ( see previous  function)
pure virtual

◆ count()

user code seldom needs to call this function directly ZMerrno count ( )

◆ erase()

user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno ZMerrno while ZMerrno to note the handler and logger used when the exception was ZMthrow n etc The resulting pointer should generally be checked against in case ZMerrno does not go back as far as requested ZMerrno for there is a loop of known ignorable all nonetheless duly recorded by the handler These exceptions can be erase ( )

◆ get() [1/2]

user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno ZMerrno get ( ) const

◆ get() [2/2]

user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno ZMerrno while ZMerrno get ( )

◆ handlers()

and for determining whether the exception instance can safely be ignored by the user code The Exceptions package includes a number of pre defined handlers ( listed  below)

◆ intended() [1/2]

The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw but will have no further affect on subsequent control flow after be thrown if its severity is ZMexERROR or but be ignored if of a lesser severity the intended ( direct or  indirect)

◆ intended() [2/2]

The given behavior will apply to any exceptions ZMthrow n after the logger has been provided the handler invokes the logger Available loggers Here is a list of the standard loggers that are defined via the Exceptions package Each is accompanied by a brief description of its the intended ( direct or  indirect) &

◆ logged()

ought always be logged ( but may be  sensible,
if hundreds of the same error are intentionally  ignored,
to stop logging each  one 
)

◆ loggers()

it is not responsible for determining or formatting any message The Exceptions package includes a few pre defined loggers ( listed  below)

◆ name() [1/2]

user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno name ( )

◆ name() [2/2]

user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno name ( ) const
pure virtual

◆ occurrence()

Ouch may be arbitrary text to be associated with this particular occurrence ( exception  instance)

◆ prefix()

any previously defined ZMexception may be used as the parent Oops is the exception s name as it is to appear in the log Such a quoted exception name string should for clarity be closely related to the actual name but as shown here might omit some package identifying baggage ExcTest is the logged message prefix ( normally indicating the  package,
facility  ,
or program giving rise to the  message 
)
new

◆ running()

logging can probably cease although we can make it safe to continue running ( e.  g.,
by supplying a default value instead of a value we can 't for some reason  calculate 
)

◆ size()

user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno size ( )

Referenced by CLHEP::HepGenMatrix::Alloc< T, size >::allocate(), CLHEP::HepGenMatrix::delete_m(), dist_layout(), CLHEP::RandGaussZiggurat::fireArray(), CLHEP::RandSkewNormal::fireArray(), CLHEP::RandExponential::fireArray(), CLHEP::RandChiSquare::fireArray(), CLHEP::RandPoisson::fireArray(), CLHEP::RandBinomial::fireArray(), CLHEP::RandPoissonT::fireArray(), CLHEP::RandGamma::fireArray(), CLHEP::RandGaussQ::fireArray(), CLHEP::RandGauss::fireArray(), CLHEP::RandExpZiggurat::fireArray(), CLHEP::RandLandau::fireArray(), CLHEP::RandStudentT::fireArray(), CLHEP::RandPoissonQ::fireArray(), CLHEP::RandGaussT::fireArray(), CLHEP::RandMultiGauss::fireArray(), CLHEP::RandBreitWigner::fireArray(), CLHEP::RandGeneral::fireArray(), CLHEP::RandFlat::fireArray(), CLHEP::MTwistEngine::flatArray(), CLHEP::Hurd288Engine::flatArray(), CLHEP::Hurd160Engine::flatArray(), CLHEP::HepJamesRandom::flatArray(), CLHEP::RanecuEngine::flatArray(), CLHEP::NonRandomEngine::flatArray(), CLHEP::Ranlux64Engine::flatArray(), CLHEP::RandEngine::flatArray(), CLHEP::RanshiEngine::flatArray(), CLHEP::TripleRand::flatArray(), CLHEP::DualRand::flatArray(), CLHEP::DRand48Engine::flatArray(), CLHEP::RanluxEngine::flatArray(), CLHEP::HepRandom::flatArray(), layout(), Genfun::RKIntegrator::RKData::lock(), n_spt_pimpl::file::read(), n_spt_pimpl::file::impl::read(), CLHEP::RandGaussZiggurat::shootArray(), CLHEP::RandSkewNormal::shootArray(), CLHEP::RandExponential::shootArray(), CLHEP::RandChiSquare::shootArray(), CLHEP::RandExpZiggurat::shootArray(), CLHEP::RandBinomial::shootArray(), CLHEP::RandGamma::shootArray(), CLHEP::RandGaussQ::shootArray(), CLHEP::RandGauss::shootArray(), CLHEP::RandPoissonT::shootArray(), CLHEP::RandBreitWigner::shootArray(), CLHEP::RandPoisson::shootArray(), CLHEP::RandStudentT::shootArray(), CLHEP::RandGaussT::shootArray(), CLHEP::RandLandau::shootArray(), CLHEP::RandPoissonQ::shootArray(), CLHEP::RandFlat::shootArray(), CLHEP::RandGeneral::shootArray(), and user_layout().

◆ ZMex()

Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix ZMex ( or  ,
in the case of the  preprocessor,
"ZMEX"   
)

◆ ZMexHandleViaParent()

subsequent instances will be thrown after handling ZMexHandleViaParent ( )

◆ ZMexIgnoreAlways()

The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw ZMexIgnoreAlways ( )

Referenced by main().

◆ ZMexLogViaParent()

it is not responsible for determining or formatting any message The Exceptions package includes a few pre defined implementing several commonly wanted logging behaviors Each exception class is associated with a logger to be applied to all ZMthrow n instances of that class By default this logger implements the behavior known as ZMexLogViaParent ( )

◆ ZMexThrowErrors()

The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw but will have no further affect on subsequent control flow ZMexThrowErrors ( )

Referenced by zmex::ZMhandler().

◆ ZMthrow()

any previously defined ZMexception may be used as the parent Oops is the exception s name as it is to appear in the log Such a quoted exception name string should for clarity be closely related to the actual name but as shown here might omit some package identifying baggage ExcTest is the logged message ZMthrow ( )

Variable Documentation

◆ above

In the example above

Definition at line 49 of file mechanics_ZMx.txt.

◆ Alternatively

Alternatively

Definition at line 179 of file mechanics_ZMx.txt.

◆ behavior

The given behavior will apply to any exceptions ZMthrow n after the logger has been provided the handler invokes the logger Available loggers Here is a list of the standard loggers that are defined via the Exceptions package Each is accompanied by a brief description of its behavior

Definition at line 188 of file mechanics_ZMx.txt.

◆ Brown

Introduction to the Use of Zoom Exceptions W E Brown

Definition at line 3 of file mechanics_ZMx.txt.

◆ clashes

Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix we use ZMexception as the name of the class from which all other exception classes all ZOOM generated ZMexception classes will use at least ZMx as their name prefix More to avoid internal name clashes

Definition at line 21 of file mechanics_ZMx.txt.

◆ Dest2

The given behavior will apply to any exceptions ZMthrow n after the logger has been provided the handler invokes the logger Available loggers Here is a list of the standard loggers that are defined via the Exceptions package Each is accompanied by a brief description of its the ostream& Dest2

Definition at line 282 of file mechanics_ZMx.txt.

◆ encountered

if encountered

Definition at line 160 of file mechanics_ZMx.txt.

◆ established

The given behavior will apply to any exceptions ZMthrow n after the logger has been established

Definition at line 255 of file mechanics_ZMx.txt.

◆ events

typically not worth logging since it s probably just a temporary placeholder ZMexINFO In the normal course of events

Definition at line 132 of file mechanics_ZMx.txt.

◆ example

We have the boost methods returning HepLorentzVector &rather than so things can be chained we feel the boost methods along an boostZ in really ought to be in the main part of the header ZOOM does several checks to see that the boost vector is not tachyonic we will forego these and use the CLHEP implementations Methods acting on containers of for example

Definition at line 382 of file mechanics_ZMx.txt.

◆ exceptions

user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno ZMerrno while ZMerrno to note the handler and logger used when the exception was ZMthrow n etc The resulting pointer should generally be checked against in case ZMerrno does not go back as far as requested ZMerrno for there is a loop of known ignorable exceptions

Definition at line 90 of file mechanics_ZMx.txt.

◆ handling

The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw but will have no further affect on subsequent control flow after handling

Definition at line 206 of file mechanics_ZMx.txt.

◆ happened

often useful for progress reporting and for debugging purposes ZMexWARNING Something unusual has happened

Definition at line 136 of file mechanics_ZMx.txt.

◆ HepTuple

Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix we use ZMexception as the name of the class from which all other exception classes all ZOOM generated ZMexception classes will use at least ZMx as their name prefix More to avoid internal name the names start with a short string identifying the e g ZMxHep for HepTuple

Definition at line 22 of file mechanics_ZMx.txt.

◆ Here

Here

Definition at line 81 of file mechanics_ZMx.txt.

◆ higher

The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw but will have no further affect on subsequent control flow after be thrown if its severity is ZMexERROR or higher

Definition at line 214 of file mechanics_ZMx.txt.

◆ ignore

always safe to ignore

Definition at line 125 of file mechanics_ZMx.txt.

◆ ignored

must always be logged and never be ignored

Definition at line 160 of file mechanics_ZMx.txt.

◆ instance

subsequent instances will be thrown after handling a logger is the term for an instance of a class that records to a designated destination a ZMthrow n exception A logger is responsible only for routing the message associated with an exception instance

Definition at line 235 of file mechanics_ZMx.txt.

◆ intended

it s generally safe to ignore the warning because you ll probably get just about the result you intended

Definition at line 138 of file mechanics_ZMx.txt.

◆ interesting

user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still since the user counter was last ZMerrno while ZMerrno ZMerrno while ZMerrno to note the handler and logger used when the exception was ZMthrow n etc The resulting pointer should generally be checked against in case ZMerrno does not go back as far as requested ZMerrno for there is a loop of known ignorable all nonetheless duly recorded by the handler These exceptions can be more interesting

Definition at line 385 of file mechanics_ZMx.txt.

◆ logged

if should always be reported to the software s developers and or maintainers Using handlers In the Exceptions a handler is the term for an instance of a class that processes a ZMthrow n exception A handler is responsible for having the exception instance logged

Definition at line 168 of file mechanics_ZMx.txt.

◆ logging

typically not worth logging since it s probably just a temporary placeholder ZMexINFO In the normal course of here is news worth logging

Definition at line 132 of file mechanics_ZMx.txt.

◆ Note

The given behavior will apply to any exceptions ZMthrow n after the handler has been established Available handlers Here is a list of the five standard handlers that are defined via the Exceptions package Each is accompanied by a brief description of its after become the object of a C throw but will have no further affect on subsequent control flow after be thrown if its severity is ZMexERROR or but be ignored if of a lesser severity Note

Definition at line 218 of file mechanics_ZMx.txt.

◆ occurrence

line identifies the specific line of source text giving rise to this occurrence

Definition at line 103 of file mechanics_ZMx.txt.

◆ Oct

Introduction to the Use of Zoom Exceptions W E Oct

Definition at line 3 of file mechanics_ZMx.txt.

◆ package

if should always be reported to the software s developers and or maintainers Using handlers In the Exceptions package

Definition at line 21 of file mechanics_ZMx.txt.

◆ problem

ought always be logged ZMexFATAL We can make no representations as to the state of any part of the even of software parts not obviously associated with the failed intended action and even if you try to handle the problem

Definition at line 156 of file mechanics_ZMx.txt.

◆ recorded

user code seldom needs to call this function directly ZMerrno whether or not they are still recorded ZMerrno whether or not they are still recorded

Definition at line 351 of file mechanics_ZMx.txt.

◆ software

ought always be logged ZMexFATAL We can make no representations as to the state of any part of the software

Definition at line 154 of file mechanics_ZMx.txt.

◆ state

ought always be logged and essentially never be ignored ZMexPROBLEM The software has reached a logically impossible internal state

◆ take

often useful for progress reporting and for debugging purposes ZMexWARNING Something unusual has but we have a quite reasonable action to take

Definition at line 137 of file mechanics_ZMx.txt.

◆ thus

thus

Definition at line 328 of file mechanics_ZMx.txt.

◆ timestamp

Thu timestamp

Definition at line 110 of file mechanics_ZMx.txt.

◆ typically

Introduction to the Use of Zoom Exceptions W E last revised Jan Introduction This summary describes the mechanics decided on for creating and throwing a ZMexception as implemented by the zoom Exceptions package Note that all public C symbols used within this Exceptions class begin with the unlikely prefix we use ZMexception as the name of the class from which all other exception classes all ZOOM generated ZMexception classes will use at least ZMx as their name prefix More typically

Definition at line 20 of file mechanics_ZMx.txt.

◆ unit

exctest1 cc this occurrence arose from this associated compilation unit

Definition at line 113 of file mechanics_ZMx.txt.

Referenced by HepGeom::Transform3D::Transform3D().

◆ Warning

Ouch may be arbitrary text to be associated with this particular as described below Resulting log message Assuming that the ExcTest program has been compiled with appropriate compiler switches that enable use of the logged message resulting from the above ZMthrow (...) example will be W it is considered a Warning

Definition at line 91 of file mechanics_ZMx.txt.

◆ yourself

logging can probably cease although we can make it safe to continue you probably won t get the result you expected unless you handle this yourself

Definition at line 145 of file mechanics_ZMx.txt.

◆ ZMxOops

it is important to be consistent ZMexception is the name of the parent exception class of ZMxOops

Definition at line 51 of file mechanics_ZMx.txt.

Referenced by main().