Are there classes that Zelix KlassMaster can't reliably process automatically?

Some classes cannot be automatically and reliably obfuscated or have names changed without needing some explicit exclusions. Examples are classes that use the Java Reflection API by hardcoding package, class, field or method names in a string and then • at runtime, test a class, field or method's name against that string, • create Class, Field, Method or Constructor instances at runtime using that string. Zelix KlassMaster can automatically handle many simple Reflection API calls.

However, if Zelix KlassMaster opens a class that it might not be able to process reliably then it reports the fact using the "Class Open Warnings" screen. See the answer to Q12 for more detail on the "Class Open Warnings" screen and the methods that trigger it. Zelix KlassMaster may still be able to automatically process classes that appear in the Class Warnings list.

For example, calls to Class.getName() are often made purely for debugging purposes. Also, in certain situations, Zelix KlassMaster can change ... more.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.