Most objects in Langband is created lazily. This means that an object may be created but may not be fully initialised and filled with appropriate values right away. The normal CL/CLOS mechanisms deal with the actual creation of the bare object, but non-trivial objects should also be "activated", ie get proper values on all variables. The object in question must be returned, failure to do so may lead to a situation where the system assumes the object is invalid.
(ACTIVATE-OBJECT (OBJ ACTIVATABLE)) [method] |
Calls | (SETF SLOT-VALUE), CALL-NEXT-METHOD, LANG-WARN, NEXT-METHOD-P and TYPE-OF | |
Location |
(ACTIVATE-OBJECT (OBJ LEVEL)) [method] |
Calls | (SETF DUNGEON.ACTIVE), CALL-NEXT-METHOD, LANG-WARN, LEVEL.DUNGEON, NEXT-METHOD-P and TYPE-OF | |
Location |
(ACTIVATE-OBJECT (OBJ HOUSE) &KEY (OWNER NIL) (VAR-OBJ *VARIANT*) (LEVEL *LEVEL*)) [method] |
Calls | (SETF HOUSE.OWNER), ACCEPTABLE-OWNER?, FIND-OWNER-FOR-HOUSE, HOUSE.OWNER and WARN | |
Location |
(ACTIVATE-OBJECT (OBJ RANDOM-LEVEL) &KEY LEAVE-METHOD PLAYER) [method] |
Calls | (SETF CAVE-FLOOR), GET-FLOOR-TYPE, LEVEL.DUNGEON, LOCATION-X and LOCATION-Y | |
Location |
(ACTIVATE-OBJECT (OBJ STORE)) [method] |
Calls | (SETF STORE.SELLS), CALL-NEXT-METHOD, ERROR, MAKE-STORE-SALES-LIST, STORE.ID and STORE.SELLS | |
Location |
This documentation was generated Autumn 2003 from the original sources by Albert v.0.4.9.