EAM: Expansive Access Modifiers in OOP

Elements in OOP are classified under maximum five access modifiers which are: public, private, protected and etc. Although, they are useful to restrict the access to the object oriented elements, they are not as restricting as enough and there isnpsilat any approach to change or customize them and therefore, their definitions arenpsilat modifiable and are the same for all systems. Moreover, all access types to an object which are read, write, update and so on, can totally be granted or denied at the same time. So, itpsilas not possible to have a situation in which the permission of writing to an attribute is denied while reading the amount of it is granted. Furthermore, it is not possible for programmers to define new required access modifiers because of inflexibility, inextensibility and coarse granularity of current access modifiers. For example, defining two attributes in a class by different access rights on them is not possible. Besides, using current access modifiers we canpsilat limit the access of some methods of a class not only to another class but also to an attribute of their own classes. In this paper, we define expansive access modifier (EAM) which includes who (as a subject of an access) may request an access (read, write, etc.) to what element (as a target) as well as some additional control parameters. This approach is the solution without current drawbacks of access modifiers.