https://sourceforge.net/p/rejava/feature-requests/47/2007-04-14T20:33:30ZRecent changes to 47: Access Modifier validation2007-04-14T20:33:30Z2007-04-14T20:33:30ZSami Koivuhttps://sourceforge.net/u/koivusa/https://sourceforge.net0eac6fba44c69df19ec665c338febf4e9e673c12

<div class="markdown_content"><p>reJ allows the user to, for example, create a method which is at the same time "public" and "private".</p> <p>For 99.5% of the cases/users, this situation makes no sense and logical assignment of asses modifiers should be enforced by reJ.</p> <p>However it would be highly interesting to let an advanced user create situations which are normally deemed illegar by the class file verifier.</p> <p>One suggestion is to set the level of integrity checking in the preferences of reJ, that would by default not allow a public and private method, but which could be set to low integrity checking by the advanced user for the purposes of testing the class file verifier, for example.</p></div>