object<-unlock

Documentation
- Reference manual
- Packages
  - XPCE
    - Classes
      - class object
        
        Get methods
        
        object<-_arg
        
        object<-_arity
        
        object<-_class_name
        
        object<-_flags
        
        object<-_inspect
        
        object<-_man_id
        
        object<-_references
        
        object<-_slot
        
        object<-_class
        
        object<-all_constraints
        
        object<-all_get_methods
        
        object<-all_hypers
        
        object<-all_send_methods
        
        object<-all_attributes
        
        object<-attribute
        
        object<-class
        
        object<-class_name
        
        object<-class_variable_value
        
        object<-clone
        
        object<-convert
        
        object<-create_context
        
        object<-find_all_send_methods
        
        object<-find_hyper
        
        object<-functor
        
        object<-get_class
        
        object<-get_hyper
        
        object<-send_method
        
        object<-get_method
        
        object<-get_sub
        
        object<-get_super
        
        object<-get_vector
        
        object<-hypered
        
        object<-inspect
        
        object<-lock_object
        
        object<-object_reference
        
        object<-print_name
        
        object<-protect
        
        object<-references
        
        object<-report_to
        
        object<-self
        
        object<-slot
        
        object<-storage_reference
        
        object<-unlock

object <-unlock: -> unchecked

Unlock object and return object<-self. If, after unlocking, the object has no references, it will be pushed on the‘anser stack’, making it visible to the incremental garbage collector.

In combination with object->lock_object, this method may be used to disconnect an object from its environment, handing it back to the incremental garbage collector. An example can be found in emacs_window<-prompt, a part of PceEmacs.

Assume we have a chain object holding a point and we want to delete the object from the chain without deleting the point. Direct usage of chain->delete may destroy the point. The following code avoids this:

send(Point, lock_object, @on),
send(Chain, delete, Point),
get(Point, unlock, _).