PCE version 4C man_modulenamespaceid_tablemodified current_idOIxNclass/constantN referenceC hash_tablerefersizeOIxaIsNV.constant.summaryCman_variable_card identifiermodule last_modifiednamesummary descriptionsee_alsoinheritdefaultsOIxNV.constant.summaryRICdateOIx+ùQ%NsummarynCstringOIxQShort description for documentation purposes. Similar to `class <-summary', etc.nnnsNV.constant.nameOIxNV.constant.nameRIOIx+ùPéNnamenOIxbName of the constant. Note that <-print_name (used by class text_item) returns <-name by default.nnnsNM.constant.S.initialiseCman_method_card identifiermodule last_modifiednamesummary descriptionsee_alsoinherit diagnosticsdefaultsbugsOI xNM.constant.S.initialiseRIOI x,|¼ N initialisenOI xâCreate a constant from its name and summary. The corresponding slots are filled and the created instance is ->protect'ed against the garbage collector. It is very uncommon for application programmers to define new constants.nnnnnsN C.constantCman_class_card identifiermodule last_modifiednamesummary descriptionsee_alsoinherituser_interfacebugsOI xN C.constantRIOI x.ïbÌNconstantnOIxëInstances of class constant represent unique values. This uniqueness is represented and guaranteed by the object-reference. Class constant defines the instance variables <-name and <-summary for documentation purposes. The system defines the following constants: @nil `Nothing, not-filled' @default `Use default value' The user may create constants for a specific application. Constants may not be deleted as they are automatically protected using ->protect. See also class bool.CchainsizeOIxIEN$class/bool$C.boolXnnnXuCnumber O Ixx