Programming variables
[Functionality by programming task]
Collaboration diagram for Programming variables:
|
Modules | |
| Programming views for variables | |
| Generic modification events and propagation conditions | |
Classes | |
| class | Gecode::VarArray< Var > |
| Variable arrays More... | |
| class | Gecode::PrimArgArray< T > |
| Argument array for primtive types. More... | |
| class | Gecode::VarArgArray< Var > |
| Argument array for variables. More... | |
| class | Gecode::VarBase |
| Base-class for variable implementations. More... | |
| class | Gecode::VarTypeProcessorBase |
| Base-class for variable type processor. More... | |
| class | Gecode::VarTypeProcessor< VTI, PC, MED > |
| Variable type processor More... | |
| class | Gecode::Variable< VTI, PC, MED > |
| Base-class for variable implementations. More... | |
Enumerations | |
| enum | Gecode::VarTypeId { Gecode::VTI_INT, Gecode::VTI_SET, Gecode::VTI_LAST, Gecode::VTI_NOIDX = 0 } |
| Variable type identifiers More... | |
Enumeration Type Documentation
|
|
Variable type identifiers Each variable type must have a unique variable type identifier. The kernel supports at most eight different variable type identifiers. If you want to add your own variable type, you have to make sure that file is created in the subdirectory vti. The names of the file defines the name of the variable type identifier (for example, if the name of the file is INT, it defines the identifier VTI_INT). |