This content has been marked as final. Show 1 reply
One more possible error in the same section:
Java addresses this problem by generating loader constraints to validate type consistency when the types being used are coming from different defining class loaders. For the example, the VM generates a constraint SpoofedL1 = SpoofedL2....
Wait, isn't this a constraint about types coming from different initiating class loaders?
This section is extremely detailed and interesting. A little more internal consistency would make it easier to understand.