creating an array of objects?

Question

It seems like this question gets asked frequently, but having looked through all of them, I find I'm still without aid. I'm taking my first step into oop, and I need to create an object with an attribute "Products" that is an array of up to 7 possible objects of class "Product". I just just barely understand the {get;set;} method, and am reading up on it, but I was hoping I could get some help with the syntax of what I'm trying to do here. I'm using C#. My code is below:

public class Submission 
{

    public Submission() {}
    public int SubmissionId {get;set;}

    public int CustId {get;set;}

    public int BroId {get;set;}

    public int Coverage {get;set;}

            public Array Products // what goes here? It's a mystery. 
}

Joel Coehoorn · Accepted Answer · 2011-05-31 15:46:51Z

1

In this case, I think you don't want an auto-implemented property. Instead, do it like this:

//backing store for your public property
private Product[] _products = new Product[7];

public Product[] Products { get {return _products;}}

and then in the constructor:

foreach(var item in _products) {item = new Product(); }

You could do this with a private setter rather than an explicit backing store, but I think this way is easier as far as setting up the size of the array goes.

Notice that I only provided a getter for the property. You don't want a setter, as that would allow someone to replace your property with a whole new array. Just providing a getter will still allow someone to manipulate the property. Also, normally I would recommend a collection rather than an array for this, but since you want a fixed-size for the number of items an array might be a better fit.

edited May 31, 2011 at 15:46

answered May 31, 2011 at 15:41

Joel Coehoorn

418k114 gold badges582 silver badges820 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Anthony Pegram Over a year ago

Any reason why you'd prefer an explicit backing field rather than simply having a private setter?

Joel Coehoorn Over a year ago

@Anthony - because of the [7] in the backing store. I'd use a private setter for lists and other collections. 6 of 1, 1/2 dozen of the other, really.

BAKeele · Accepted Answer · 2011-05-31 15:45:35Z

1

If you are up to using generic collections, I would use:

 public List<Product> Products { get; private set; }

or some variation thereof.

edited May 31, 2011 at 15:45

answered May 31, 2011 at 15:39

BAKeele

3071 silver badge5 bronze badges

2 Comments

Joel Coehoorn Over a year ago

You probably don't want a setter for this property.

BAKeele Over a year ago

Probably not. Updated to reflect as such.

Nathan Anderson · Accepted Answer · 2011-05-31 15:39:37Z

0

You can write it like this:

public Products[] { get; set; }

and in the constructor of your class:

public Submission() { Products = new Product[7]; }

answered May 31, 2011 at 15:39

Nathan Anderson

6,87830 silver badges30 bronze badges

Comments

Daniel A. White · Accepted Answer · 2011-05-31 15:38:50Z

-1

Use an IList. You can use the auto property with it.

answered May 31, 2011 at 15:38

Daniel A. White

192k49 gold badges389 silver badges473 bronze badges

1 Comment

Ace Troubleshooter Over a year ago

Why was the IList downvoted? I saw Joel suggested it first, and then edited to another method. Any reason an IList is a bad idea?

Collectives™ on Stack Overflow

creating an array of objects?

4 Answers 4

2 Comments

2 Comments

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

2 Comments

2 Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related