Another way to look at this with an example ...
In .Net, you can use the Reflection.Emit namespace to generate and compile code at runtime.
For example, you can create an βIDEβ with a text field that C # accepts. When you click a button that C # can compile the .Net framework into a user library that loads a dynamically or fully executable executable that starts as a new process.
This is insanely powerful when combined with the rest of the System.Reflection namespace. You can scan objects at runtime and compile your own code based on any criteria that you like.
That said ... Problems usually outweigh the benefits in most cases. This is mainly a serious security issue, especially when working on a consumer device.
You could create an application that would have nothing close to the malicious code, get it under Apple control, then download the application download code from your web server, compile it and execute it. This new code will not be checked ...
In fact, there is no good reason for this in the consumer application.
source share