PCE version 4C man_modulenamespaceid_tablemodified current_idOIxNerrorsN referenceC hash_tablerefersizeOIxNbothIsN!.bad_type_syntaxCman_error_card identifiermodule last_modifiednamesummary descriptionsee_alsoinheritOIxN!.bad_type_syntaxRICdateOIx+I Nbad_type_syntaxnCstringOIxuThis error is generated on a syntax error in a type specification. See `type <-convert' for valid type declarations.CchainsizeOIxIEN$class/type$M.type.G.convertXnsN!.replaced_by_colourOIxN!.replaced_by_colourRIOIx3mHNreplaced_by_colournOI x%O: replaced by colour(%N) The X11 versions allows colours to be replaced by pixmap objects, The MS-Windows version does not allow this. If a pixmap object is specified as a colour, the system will check whether the pixmap is derived from one of the standard grey-patterns (@grey25_image, etc.) and replace the pixmap by a grey colour. If this fails it will use colour(black). This error is raised if a pixmap is replaced. You may redefine the mapping by attaching an `object ->attribute' named `replacement_colour' to the pixmap.nnsN!.bad_selectorOI xN!.bad_selectorRIOI x,}EN bad_selectornOI x{The error is generated by the virtual machine operations send() and get() if the selector cannot be translated into a name.OI xIeN!.argument_typeeN$objects$O.vmi_sendEN$objects$O.vmi_getXnsN!.replaced_colourOIxN!.replaced_colourRIOIx3m|Nreplaced_colournOIxsformat: %O: replaced by colour(%N) A colour was replaced by a (close) colour because the system colour map is full.nnsN!.cannot_save_objectOIxN!.cannot_save_objectRIOIx+QNcannot_save_objectnOIxThis error is raised by `object ->save_in_file' if it encounters an object it cannot save. The object will be saved as @nil. An object cannot be saved iff is has instance variables of type `alien:' and the object's class variable `save_function' is not defined (i.e. 0). The methods `object ->save_in_file' and `file <-object' are intended to save *data* objects and *not* to save *UI* objects. PCE can save almost all data objects, but only very few of the X-window related objects.OIxIEN%$class/object$M.object.S.save_in_fileXnsN!.argument_typeOIxN!.argument_typeRIOIx+M/N argument_typenOIxThis error is raised by variables and methods (i.e. behaviour) and various other methods to indicate that the n-th argument is not of the requested type. Argument counting starts *after* the selection: send(@display, inform, 'Hello %s', universe). ^^1-st^^ ^^2-nd^^OIxIeN!.argument_counteN!.bad_selectoreN $predicates$3EN $predicates$2XnsN!.freed_value_valueOIxN!.freed_value_valueRIOIx+YNfreed_value_valuennOIxIeN!.freed_key_valueeN!.freed_slot_valueEN$class/object$M.object.S._checkXnsN!.freed_cell_valueOIxN!.freed_cell_valueRIOIx+YNfreed_cell_valuennOIxIeN!.freed_slot_valueEN$class/object$M.object.S._checkXnsN!.argument_countOIxN!.argument_countRIOI x+LNargument_countnOI!xThis error is raised by variables and methods (i.e. behaviour) when the number of arguments supplied cannot be matched against the type-checking vector.OI"xIEN!.argument_typeXnsN!.freed_slot_valueOI#xN!.freed_slot_valueRIOI$x+ZSNfreed_slot_valuenOI%xfRaised by `object ->_check' to indicate that a particular slot contains an object that has been freed.OI&xIeN!.freed_value_valueeN!.freed_key_valueeN!.freed_element_valueeN!.freed_cell_valueEN$class/object$M.object.S._checkXnsN!.converted_return_valueOI'xN!.converted_return_valueRIOI(x+NNconverted_return_valuenOI)xThis error is raised if the value returned by a get_method object's implementation does not match `get_method <-return_type' but could be translated. The method will return with the translated type.OI*xIeN*$class/get_method$V.get_method.return_typeEN!.bad_return_valueXnsN !.backup_fileOI+xN !.backup_fileRIOI,x+1gN backup_filennOI-xIEN$class/file$M.file.S.backupXnsN !.creatingOI.xN !.creatingRIOI/x.7NcreatingnOI0xFormat: %O: Creating flag set This error is generated by `object ->_check' (normally invoked through checkpce/0). It indicates that the object was allocated, but it's ->initialise method has not (yet) returned. This may be the case if a fatal error was trapped or a Prolog abort was generated during the execution of the ->initialise method. The object should be expected to be in inconsistent state. In most cases you can safely continue using the image though as the object should normally not be referenced.OI1xIEN$class/object$M.object.S._checkXnsN!.already_has_parentOI2xN!.already_has_parentRIOI3x+,Nalready_has_parentnnOI4xIEN$$class/event_node$M.event_node.S.sonXnsN !.bad_fileOI5xN !.bad_fileRIOI6x+ONbad_filenOI7xThis error is raised when the system attempts to read a file that should be in a particular format, but the file is not of this format. Common types: # object Raised by `file <-object' if the file is not created using `object ->save_in_file' # image Raised by `image ->load' if the file does not contain an image (bitmap) description in one of the formats recognised by XPCE,.OI8xIeN$class/image$M.image.S.loadEN$class/file$M.file.G.objectXnsN!.no_behaviourOI9xN!.no_behaviourRIOI:x,rN no_behaviournOI;xYThe error `no_behaviour' is raised by the virtual machine operations send() and get() if there is no implementation for the requested selector on the requested object. By changing the <-kind of this error, not-implemented behaviour may be ignored (<-kind: ignored); just printed (<-kind: warning) or trap the tracer (<-kind: error). By default, undefined behaviour is just printed. For program development we advice to switch <-kind of this error to `error'. This may be achieved using the `Error Browser' or using the following line in your ~/.xpcerc: :- send(error(no_behaviour), kind, error).nnsN!.bad_vector_usageOIxRaised by the various methods that accept a vector as a sequence of arguments. The syntax of such methods is always: unchecked..., vector, [int] See `object ->send_vector'OI?xIEN$$class/object$M.object.S.send_vectorXnsN!.bad_slot_valueOI@xN!.bad_slot_valueRIOIAx+YNbad_slot_valuennOIBxIEN$class/object$M.object.S._checkXnsN!.freed_key_valueOICxN!.freed_key_valueRIOIDx+YNfreed_key_valuennOIExIeN!.freed_value_valueeN!.freed_slot_valueEN$class/object$M.object.S._checkXnsN!.checked_objectsOIFxN!.checked_objectsRIOIGx+R Nchecked_objectsnOIHx]This message is raised by `object ->_check' to indicate the number of objects it has checked.OIIxIeN$predicates$25EN$class/object$M.object.S._checkXnsN !.no_variableOIJxN !.no_variableRIOIKx+XsN no_variablennOILxIEN$class/object$M.object.S._checkXnsN!.bad_return_valueOIMxN!.bad_return_valueRIOINx+H+Nbad_return_valuenOIOxvThis error is generated if a method returns a value that cannot be converted into the type `get_method <-return_type'.OIPxIeN!.converted_return_valueEN*$class/get_method$V.get_method.return_typeXnsN!.freed_element_valueOIQxN!.freed_element_valueRIOIRx+YNfreed_element_valuennOISxIeN!.freed_slot_valueEN$class/object$M.object.S._checkXnsN!.bad_file_nameOITxN!.bad_file_nameRIOIUx+ON bad_file_namenOIVxdThis error is raised if an illegal filename is encountered. A filename is considered illegal iff: # It is too long (maximum lenght depends on the operating system used). # It starts with ~username and `username' is not the name of an existing user (Unix only) # There is a construct $VARNAME and `VARNAME' is not the name of an existing variable.nnsN!.killed_on_exitOIWxN!.killed_on_exitRIOIXx+FNkilled_on_exitnOIYxaPCE kills all inferior processes while exiting. This message is printed for each process killed.OIZxIeN$class/pce$V.pce.exit_messagesEN$class/process$C.processXnXaCnumberOI[xx