rooType
class description - source file - inheritance tree
public:
rooType rooType()
rooType rooType(void* imp)
rooType rooType(rooType&)
virtual void ~rooType()
TClass* Class()
const rooModule& defined_in_module() const
Int_t dimension() const
virtual Bool_t is_basic_type() const
virtual Bool_t is_bidirectional_relationship_type() const
virtual Bool_t is_ref_type() const
virtual Bool_t is_relationship_type() const
virtual Bool_t is_string_type() const
virtual Bool_t is_type() const
virtual Bool_t is_unidirectional_relationship_type() const
virtual Bool_t is_varray_basic_type() const
virtual Bool_t is_varray_embedded_class_type() const
virtual Bool_t is_varray_ref_type() const
virtual Bool_t is_varray_type() const
virtual TClass* IsA() const
virtual void ShowMembers(TMemberInspector& insp, char* parent)
virtual void Streamer(TBuffer& b)
virtual Int_t type_number() const
rooCollectionTypeItr used_in_collection_type_begin()
rooCollectionTypeItr used_in_collection_type_end()
rooPropertyItr used_in_property_begin()
rooPropertyItr used_in_property_end()
rooRefTypeItr used_in_ref_type_begin()
rooRefTypeItr used_in_ref_type_end()
protected:
rooModule* fDefinedInModule module containing the described type
See also
-
rooClass, rooPropertyType
rooType corresponds to d_Type Class
The abstract class rooType represents descriptors for types in the schema
of the federated database.
______________________________________________________________________________
About Type Descriptors
An instance of any concrete class derived from d_Type is called a type
descriptor;it provides information about a particular type, called its
described type. Concrete derived classes represent descriptors for:
- Classes
- Attribute types
- Relationship types
Because this class is abstract, you never instantiate it; instead, you work
with instances of its concrete derived classes. You should not derive your
own classes from this class.
rooType()
default ctor. , for internal use only
~rooType()
dtor, for internal use only
rooCollectionTypeItr used_in_collection_type_begin()
Gets an iterator for the collection types in the schema that are created
from the described type.
rooCollectionTypeItr used_in_collection_type_end()
Gets an iterator representing the termination condition for iteration
through the collection types that are created from the described type.
You can compare the iterator returned by used_in_collection_type_begin
with the one returned by this member function to test whether iteration
has finished.
rooRefTypeItr used_in_ref_type_begin()
Gets an iterator for the object-reference types in the schema that
reference the described type.
rooRefTypeItr used_in_ref_type_end()
Gets an iterator representing the termination condition for iteration
through the object-reference types that reference the described type.
rooPropertyItr used_in_property_begin()
Returns a property iterator that finds all properties in the schema that
use the described type.
The returned iterator gets generic property descriptors for each property
that uses the described type. You can call the is_relationship_type
member function to find out whether the described type is a relationship
type. If so, you can cast the property descriptors to relationship
descriptors; if not, you can cast the property descriptors to attribute
descriptors.
rooPropertyItr used_in_property_end()
Returns a property iterator that is positioned after the last related
property.
You can compare the iterator returned by used_in_property_begin with the
one returned by this member function to test whether iteration has
finished.
Int_t dimension() const
Returns the layout size in bytes for a value of the described type on the
platform where the current application is running.
If the described type is a class, the result is the number of bytes
required to store an instance of that class.
If the described type is a property type, the result is the number of
bytes required to store a property of this type within the data of an
instance of a class that contains the property.
Int_t type_number() const
Non-class types will be assigned a unique 32-bit AStypeNumberCode
OR-constructed with a set high bit, the ooMemberType shifted left
27, and the referenced or collected class number or referenced
ooBaseType. For class types, type_number returns the Objectivity
type number.
Bool_t is_basic_type() const
Returns kTRUE if the described type is a basic numeric type;
otherwise, kFALSE.
Bool_t is_varray_type() const
Returns kTRUE if the described type is a VArray type; otherwise, kFALSE.
Bool_t is_varray_basic_type() const
Returns kTRUE if the described type is a VArray of numeric elements;
otherwise, kFALSE.
Bool_t is_varray_embedded_class_type() const
Returns kTRUE if the described type is an embedded-class VArray type;
otherwise, kFALSE.
Bool_t is_varray_ref_type() const
Returns kTRUE if the described type is an object-reference VArray type;
otherwise, kFALSE.
Bool_t is_relationship_type() const
Returns kTRUE if the described type is a relationship type;
otherwise, kFALSE.
Bool_t is_unidirectional_relationship_type() const
Returns kTRUE if the described type is a unidirectional relationship type;
otherwise, kFALSE.
Bool_t is_bidirectional_relationship_type() const
Returns kTRUE if the described type is a bidirectional relationship type;
otherwise, kFALSE.
Bool_t is_ref_type() const
Returns kTRUE if the described type is an object-reference type
ooRef( PCclass) or ooShortRef( PCclass); otherwise, kFALSE
Bool_t is_string_type() const
Returns kTRUE if the described type is a string class; otherwise,
kFALSE. The string classes are:
- The ASCII string class ooVString
- The optimized string classes ooString( N)
- The Unicode string class ooUTF8String
- The Smalltalk string class ooSTString
Inline Functions
rooType rooType(void* imp)
Bool_t is_type() const
const rooModule& defined_in_module() const
TClass* Class()
TClass* IsA() const
void ShowMembers(TMemberInspector& insp, char* parent)
void Streamer(TBuffer& b)
rooType rooType(rooType&)
Author: Valeriy Onuchin 11/09/2000
ROOT page - Class index - Top of the page
This page has been automatically generated. If you have any comments or suggestions about the page layout send a mail to ROOT support, or contact the developers with any questions or problems regarding ROOT.