See Module

Hope this makes sense!

When a module done in ‘C’ is run through ‘Drucks’ ‘ARMalyser’ the code ends with some DATA values needing to be relocated at startup.

Ref reloc code at end of Module.

If a new – empty module is made up – and you wish to add old C/ASM code from another module – is there a strait forward way of ASM reloc code to be fed back into the new module?

If you are creating a new module, it will be written in C/assembler, and you can (usually) just call in the routines you want that were in the other module provided they are in source form. The linker will take care of what needs relocated where. I’ve recycled common routines (my DADebug routine, for instance).

If you meant to create a new module and link into functions that are actually compiled and held within another module, then no. There’s no tidy way to do such a thing, just various implementations that rely deeply in nothing changing. For example DADebug will give you an address of a WriteC-like function entry point; CLib will create a jumptable in your workspace – and both will blow up if their respective module is reloaded and it ends up in a different place in memory (somewhat likely) because all of the pointers will cease to point to anything useful…
If you don’t have a SWI to get an address, well, then that’s probably a good thing. The RMA is fragile enough as it is. ;-)