Service_ModulePostFinal
Programmer's Reference Manuals
» Service Calls
» Service_ModulePostFinal
Service_ModulePostFinal
(Service &DB)
| Entry | |
|---|---|
| R0 | Module address |
| R1 | 219 (&DB) |
| R2 | Pointer to module title |
| R3 | 0 for base instantiation, else R3 = pointer to postfix string |
| R4 | BCD version number (derived from module’s help string) |
| Exit | |
|---|---|
| R0 | Preserved |
| R1 | Preserved |
| R2 | Preserved |
| R3 | Preserved |
| R4 | Preserved |
Use
This service call is made by the kernel after a module has been finalised, including during module reinitialisation. At the time the call is made the module will not be linked into the module chain, so its SWIs etc are not available.
This service call is intended to inform clients of a module that any registrations they made with it are no longer active, and any associated handles are stale. Along with Service_ModulePostInit, this avoids the need for each module to have its own dedicated initialisation/finalisation service calls.
For modules which need to give their clients more warning (i.e. warning them before finalisation instead of after), it is also acceptable for modules to make this service call themselves, during their finalisation sequence. However there is currently no way of determining whether the call came from the kernel or from the module – programmers must consult the documentation of each module to determine whether the service call is issued manually or not.
Notes
This service call must not be claimed.
See also
Social
and
ROOL Store
Buy RISC OS Open merchandise here, including SD cards for Raspberry Pi and more.