M
Marian Edu
Guest
I'm on the Java side (no surprise I guess), do like the setAccessible option to turn off access check... guess we can take the risk of a brute force attack from the crowd that tries to find private properties/methods 
Unit testing private methods is hard anyway, most of the time I tend to go with protected/final just to get along this. Package level protection can easily be avoided with 'parallel' packages especially the way we use propath so that won't make me feel any more safe, inventive users will always find ways to lift that protection... the only joy I find is to see them suffer latter one because of that 
Continue reading...
Unit testing private methods is hard anyway, most of the time I tend to go with protected/final just to get along this. Package level protection can easily be avoided with 'parallel' packages especially the way we use propath so that won't make me feel any more safe, inventive users will always find ways to lift that protection... the only joy I find is to see them suffer latter one because of that Continue reading...