cj7hawk
Veteran Member
Hi All,
Just wondering about the group's thoughts on self-modifying code on CP/M systems.
Some people regard this as contentious while others see it as a valuable way to save space and extend the system.
In this context, I'm talking about either modifying the instruction itself, or modifying the bytes extending the instruction, so that when the instruction executes, it's functionally changed - It could be as simple as setting up a label over the top of the displacement byte in an IX/IY operation, or as complex as changing the code function that executes within a routine - eg, Changing ADD to SBC etc.
I've heard arguments supporting and denouncing it over time, but was wondering on how common a practice this is within CP/M and what people think about the practice itself.
Thanks
David
Just wondering about the group's thoughts on self-modifying code on CP/M systems.
Some people regard this as contentious while others see it as a valuable way to save space and extend the system.
In this context, I'm talking about either modifying the instruction itself, or modifying the bytes extending the instruction, so that when the instruction executes, it's functionally changed - It could be as simple as setting up a label over the top of the displacement byte in an IX/IY operation, or as complex as changing the code function that executes within a routine - eg, Changing ADD to SBC etc.
I've heard arguments supporting and denouncing it over time, but was wondering on how common a practice this is within CP/M and what people think about the practice itself.
Thanks
David