Objective-C used to support reloading but now explicitly does not (dlclose() doesn't do anything) because it's unsafe.
Xcode used to have these features (called Zero Link and fix and continue) but they were quickly removed because nobody used them.
Xcode used to have these features (called Zero Link and fix and continue) but they were quickly removed because nobody used them.
> quickly removed because nobody used them
n=1 and all that, but as a developer i used it all the time and was totally dismayed it was removed...
A famous example of self-modifying code was Microsoft's AARD code, which was decrypted on the fly to check if the user was running a competitor's OS. [1]
I always wondered if the perceived threat of runtime method constructors was an incentive for Apple to push for Swift.
Code signing and a secure enclave may help protect against local use cases, like ransomware, but doesn't protect against hybrid attacks, like granting access to 3rd parties.
Maybe this means that all binaries in 2040 should be derived from open source with AI doing the threat detection.