#47 Access Modifier validation

[Sami Koivu]

reJ allows the user to, for example, create a method which is at the same time "public" and "private".

For 99.5% of the cases/users, this situation makes no sense and logical assignment of asses modifiers should be enforced by reJ.

However it would be highly interesting to let an advanced user create situations which are normally deemed illegar by the class file verifier.

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.