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

X.cc
Go to the documentation of this file.
1 // -*- C++ -*-
2 // $Id: X.cc,v 1.3 2003/09/06 14:04:14 boudreau Exp $
4 
5 namespace Genfun {
7 
8 X_::X_()
9 {}
10 
11 X_::X_(const X_ & right) : AbsFunction(right)
12 {
13 }
14 
16 }
17 
18 double X_::operator() (double x) const {
19  return x;
20 }
21 
22 } // namespace Genfun
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 exceptions
Definition: mechanics_ZMx.txt:90
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: mechanics_ZMx.txt:20
Genfun::AbsFunction
Definition: CLHEP/GenericFunctions/AbsFunction.hh:48
X.hh
Genfun::X_::X_
X_()
Definition: X.cc:8
Genfun::X_::~X_
virtual ~X_()
Definition: X.cc:15
ZMthrow
#define ZMthrow(userExcept)
is
HepRotation and so forth isNear() norm2() rectify() static Rotation row1 row4(To avoid bloat in the code pulled in for programs which don 't use all these features, we split the implementation .cc files. Only isNear() goes into the original Rotation.cc) --------------------------------------- HepAxisAngle and HepEulerAngles classes --------------------------------------- These classes are very useful and simple structures for holding the result of a nice intuituve decomposition of a rotation there is no longer much content in the distinct ZOOM PhysicsVectors library The only content left in the library is the object files representing the various Exception objects When we build the CLHEP classes for the ZOOM we will set up so as to use ZOOM SpaceVector is(but we can disable namespace usage and most of our users do so at this point). What I do is leave Hep3Vector in the global namespace
used
When exceptions are the ZMthrow macro looks we know the try part will throw why not just consider how ZMthrow is typically used
Definition: whyZMthrowRethrows.txt:25
zmex::ZMexThrowIt
@ ZMexThrowIt
Definition: CLHEP/Exceptions/ZMexAction.h:20
code
Signatures of Hep3Vector::rotate For equivalent ZOOM axis There is no harm in leaving this axis CLHEP has implemented a first forming an identity then rotating that by axis and I leave the CLHEP code alone people are of course free to use the ZOOM originated method with signature which I believe will be faster Return types for rotateZ CLHEP and PhysicsVectors each have these three and they are identical except that the ZOOM version returns a reference to while in CLHEP they return void Having methods that alter an object return a reference to that object is convenient for certain chained and costs nothing I don t wish to potentially break ZOOM user code for no good so I have made these CLHEP method conform to this convention There are a couple of other CLHEP rotate and which use the void return but since these methods or signatures don t appear in the original ZOOM this can t break any code
Definition: minorMergeIssues.doc:115
any
this formatted text is the function s string result this method sends the formatted string s to the ostream destination specified when the logger was instantiated as its a code describing if any
Definition: ZMthrow_event_sequence.txt:148
not
if not
Definition: ZMthrow_event_sequence.txt:51
zmex::ZMthrow_
ZMexAction ZMthrow_(const ZMexception &userException, int lineNum, const char fileName[])
Definition: ZMthrow.cc:33
Genfun::X_
Definition: CLHEP/GenericFunctions/X.hh:19
When
it has advantages For I leave the ZMthrows but substitute I replaced ZMthrow with ZMthrowA in this package when will issue its message and I introduce a macro ZMthrowC which I use wherever it seems there is a sensible way to continue processing after reporting the problem When(if ever) the actual ZOOM exceptions package is incorporated into Vector ZMthrowC may eventually be handle the selective continuiing. However
Genfun::X_::operator()
virtual double operator()(double argument) const
Definition: X.cc:18
enabled
When exceptions are enabled
Definition: whyZMthrowRethrows.txt:1
does
Technical Maintenance Note for CLHEP Random Consequences of seeding JamesRandom with positive seed values greater than In the source code JamesRandom The usual way of seeding a generator is via the default which makes use of the table of and the seed is the xor of a mask which starts with a bit and the seed from the table But it and often does
Definition: JamesRandomSeeding.txt:18
like
When exceptions are the ZMthrow macro looks like
Definition: whyZMthrowRethrows.txt:13
hand
any side effects of that construction would occur twice The semantics of throw on the other hand
Definition: whyZMthrowRethrows.txt:37
x
any side effects of that construction would occur twice The semantics of throw x
Definition: whyZMthrowRethrows.txt:37
FUNCTION_OBJECT_IMP
#define FUNCTION_OBJECT_IMP(classname)
Definition: CLHEP/GenericFunctions/AbsFunction.hh:156
are
Issues Concerning the PhysicsVectors CLHEP Vector Merge The merge of ZOOM PhysicsVdectors and the CLHEP Vector package is completed The purpose of this document is to list the major issues that affected the merge of these and where relevant describe the resolutions More detailed documents describe more minor issues General Approach As agreed at the June CLHEP the approach is to combine the features of each ZOOM class with the corresponding CLHEP class expanding the interface to create a single lingua franca of what a I have placed almost all the new features in a second section of the and have created separate cc files for sensible subsets of the methods In if a program uses only the methods found in the original CLHEP very little additional code is linked in Classes The corresponding classes are
Definition: keyMergeIssues.doc:61
Genfun
Definition: CLHEP/GenericFunctions/Abs.hh:14