StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POEncapsulation of reference types inside a collection
primarykey
Id
4757071
data
AcceptedAnswerId
4757145
AnswerCount
4
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-01-21T09:10:39.497
FavoriteCount
0
LastActivityDate
2011-01-21T11:35:43.440
LastEditDate
2011-01-21T11:35:43.440
LastEditorUserId
244151
OwnerUserId
244151
ParentId
0
PostTypeId
1
Score
1
ViewCount
347
LastEditorDisplayName
text
Body
I declared a class with several properties <pre><code>class Soil { public double AnglePhi { get; set; } public double AngleDelta { get; set; } . . . } </code></pre> Now to manipulate a collection of them I built another dedicated class, only for this reason. <pre><code>class Soils { private const Byte numberOPredefined = 10; private IList<Soil> soils; public Soil this[ushort i] { get { return new Soil() { AngleDelta = soils[i].AngleDelta, ... }; } set { if (i > numberOPredefined) soils[i] = value; } } . . . } </code></pre> The logic behind this, is to protect somewhat from direct manipulation of the properties of each Soil instance. Give a copy in getter, ask for a "whole" soil object in setter. From what I red thus far, other solutions could be: make Soil class immutable, return a ReadOnly List (but then the reference types inseide can be manipulated) turn Soil class to struct (simple), augment Soil class with some logic (methods etc). I would like to ask if the above "solution" has any value at all, or is ill-defined. This is a typical situation I think, eg having a collection of reference types and want to encapsulate them. What is the typical frame of thinking in these situations ? EDIT : Ok, after reading the answers I modified the solution to this <pre><code>class Soil { private readonly double _AnglePhi; public double AnglePhi { get { return _AnglePhi; } } private readonly double _AngleDelta; public double AngleDelta { get { return _AngleDelta; } } . . } class SoilCollection { private List<Soil> _Soils; public IList<Soil> Soils { get { return _Soils.AsReadOnly(); } } . . } </code></pre> I think the Soil class needed logic inside it, and not inside another class. I 'll post if I find any shortcomings.
Tags
<c#><collections><encapsulation><indexer>
Title
Encapsulation of reference types inside a collection
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USDimi_Pel
UserOwnerUserId
1. USDimi_Pel
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POEncapsulation of reference types inside a collection
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.