Indexer:Why to use it if Public array can solve the purpose

amit_gupta14

1. If public array can solve the purpose, then why to use indexer 2.There is array member private int [] myArray = new int[100]; in class say c1. I have used the following code to use indexer public int this [int index] // Indexer declaration { get { // Check the index limits. if (index < 0 || index >= 100) return 0; else return myArray[index]; } set { if (!(index < 0 || index >= 100)) myArray[index] = value; } } It is working fine. But say there is another member private string [] myArray11 = new string[100]; in the same class along with previous member, then how to use indexer for it.

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

bilnaad22y ago
1. Yes, it's a small difference but an important one for OOP design. 2. If you know what an array is... Then question yourself what an array behaves like. Then think of what you expect from your class at this point. Does your class still has array behavior? I don't thinks so ^_^ You can have one indexer not more. Else it wouldn't be an array ^_^
amit_gupta1422y ago
1. You want to say that we try to avoid public sort of things in OOPS, that's why indexer is better option than public array. Is it the only difference? 2. private int [] myArray = new int[100]; private string [] arr=new string[100]; //I have used the following code to use indexer for myArray public int this [int index] // Indexer declaration { get { // Check the index limits. if (index < 0 || index >= 100) return 0; else return myArray[index]; } set { if (!(index < 0 || index >= 100)) myArray[index] = value; } } In above code, If I have used indexer for myArray. If I want to solve the same purpose for arr then how will it be done?
bilnaad22y ago
1. A public array doesn't solve the problem :) OOP is all about encapsulation and abstraction. That's why a public field completely destroys the purpose of OOP. You can manipulate the data it holds directly. That is, you get the actual memory reference for the fields. When you use an indexer you don't get the reference. Just a value. 2. Indexers are designed for classes that need to have array-like behavior. I don't know any array that represents many arrays of different types(or what you tried to explain :))