A dummy implementation of a concept seems to provide an interface for the concept, but calling any operation in this interface will simply signal an error. Hence, when using a dummy implementation, we can be sure that we only rely on the abstract interface but not on any implementation details, for the simple reason that there is no actual implementation. This is useful for testing or compilation against a generic implementation of a concept.
‣ IsDummyRing | ( filter ) |
The GAP filter of dummy rings.
‣ IsDummyRingElement | ( filter ) |
The GAP filter of elements of a dummy ring.
‣ IsDummyCommutativeRing | ( filter ) |
The GAP filter of dummy commutative rings.
‣ IsDummyCommutativeRingElement | ( filter ) |
The GAP filter of elements of a dummy commutative ring.
‣ IsDummyField | ( filter ) |
The GAP filter of dummy fields.
‣ IsDummyFieldElement | ( filter ) |
The GAP filter of elements of a dummy commutative ring.
‣ DummyRing ( arg ) | ( function ) |
Returns: a dummy ring
‣ DummyCommutativeRing ( arg ) | ( function ) |
Returns: a dummy commutative ring
‣ DummyField ( arg ) | ( function ) |
Returns: a dummy field
‣ IsDummyCategory ( arg ) | ( filter ) |
Returns: true
or false
The GAP category of a dummy CAP category.
‣ IsDummyCategoryObject ( arg ) | ( filter ) |
Returns: true
or false
The GAP category of objects in a dummy CAP category.
‣ IsDummyCategoryMorphism ( arg ) | ( filter ) |
Returns: true
or false
The GAP category of morphisms in a dummy CAP category.
‣ DummyCategory ( options ) | ( operation ) |
Returns: a category
Creates a dummy category subject to the options given via options, which is a record passed on to CategoryConstructor
(11.2-1). Note that the options {category,object,morphism}_filter
will be set to IsDummyCategory{,Object,Morphism}
and the options {object,morphism}_{constructor,datum}
and create_func_*
will be set to dummy implementations (throwing errors when actually called). The dummy category will pretend to support empty limits by default.
generated by GAPDoc2HTML