How to solve this classic problem?

[Daniel Billingsley]

I've got to believe this is a fairly common / classic problem, and I think
I've even read an example somewhere in my education thus far, but I sure
can't remember it.

Suppose I want to store a list of first and last names read from a file. I
think somewhere I need an ArrayList. So I have a class that stores a
private ArrayList.

I want this class to be able to return the first name, the last name, or a
"calculated " FullName... but I want to be able to set a property of this
class of say Capitalization and have it affect the results of accessing the
names. I realize it's easy enough to have a class implement an indexer that
returns the proper element of say an ArrayList of structures, but I need to
modify each part of the structure upon it's access. That would be easy
enough to do in the accessors in the structure, but the structure doesn't
really know anything about the class's Capitalization property, and I really
want to avoid having the structure also hold a Capitalization property and
having to go through the entire ArrayList every time the Class property is
changed.

I realize I could also code a GetLastName(int index) or something like that
in the class, but that seems a bit kludgey and wouldn't be as
straightforward to the users of the class as I would hope to achieve. What
I'd like to achieve when using the class is something like..

NamesList myNamesList = new NamesList();
myNamesList.Rea dFromFile("blah blah.txt");
myNamesList.Cap italization = NameCapitalizat ion.AllCaps;
Console.WriteLi ne(NamesList[1].FirstName); // Output is "DAN"
myNamesList.Cap italization = NameCapitalizat ion.ProperName;
Console.WriteLi ne(NamesList[1].FirstName); // Output is "Dan"

What's the magic ingredient I'm missing?

[Jon Skeet [C# MVP]]

Daniel Billingsley <db**********@N O.durcon.SPAAMM .com> wrote:

I've got to believe this is a fairly common / classic problem, and I think
I've even read an example somewhere in my education thus far, but I sure
can't remember it.

<snip>

I'll have a closer look at this tomorrow - it looks like an interesting
problem. I won't be able to post an answer for about 18 hours though -
but I thought I'd just post to say I *will* be looking at it later :)

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Womble One]

The indexer should clone the object, and then perform the required
capitalisation on the cloned object.
"Daniel Billingsley" <db**********@N O.durcon.SPAAMM .com> wrote in message
news:uh******** ******@tk2msftn gp13.phx.gbl...

I've got to believe this is a fairly common / classic problem, and I think
I've even read an example somewhere in my education thus far, but I sure
can't remember it.

Suppose I want to store a list of first and last names read from a file. I think somewhere I need an ArrayList. So I have a class that stores a
private ArrayList.

I want this class to be able to return the first name, the last name, or a
"calculated " FullName... but I want to be able to set a property of this
class of say Capitalization and have it affect the results of accessing the names. I realize it's easy enough to have a class implement an indexer that returns the proper element of say an ArrayList of structures, but I need to modify each part of the structure upon it's access. That would be easy
enough to do in the accessors in the structure, but the structure doesn't
really know anything about the class's Capitalization property, and I really want to avoid having the structure also hold a Capitalization property and
having to go through the entire ArrayList every time the Class property is
changed.

I realize I could also code a GetLastName(int index) or something like that in the class, but that seems a bit kludgey and wouldn't be as
straightforward to the users of the class as I would hope to achieve. What I'd like to achieve when using the class is something like..

NamesList myNamesList = new NamesList();
myNamesList.Rea dFromFile("blah blah.txt");
myNamesList.Cap italization = NameCapitalizat ion.AllCaps;
Console.WriteLi ne(NamesList[1].FirstName); // Output is "DAN"
myNamesList.Cap italization = NameCapitalizat ion.ProperName;
Console.WriteLi ne(NamesList[1].FirstName); // Output is "Dan"

What's the magic ingredient I'm missing?

[Jeffrey Tan[MSFT]]

Hi Daniel,

Thanks for posting in this group.
I think the copy data method is not a good performance way, while William's
way is suitable.
His method is checking the Capitalization property in each property's get
accessor, then you can return the suitable property format.

If you have anything unclear, please feel free to let us know.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

--------------------
| From: "Daniel Billingsley" <db**********@N O.durcon.SPAAMM .com>
| Subject: How to solve this classic problem?
| Date: Mon, 3 Nov 2003 16:11:37 -0500
| Lines: 35
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-Mimeole: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <uh************ **@tk2msftngp13 .phx.gbl>
| Newsgroups: microsoft.publi c.dotnet.langua ges.csharp
| NNTP-Posting-Host: 68-74-16-211.ded.amerite ch.net 68.74.16.211
| Path: cpmsftngxa06.ph x.gbl!TK2MSFTNG P08.phx.gbl!tk2 msftngp13.phx.g bl
| Xref: cpmsftngxa06.ph x.gbl microsoft.publi c.dotnet.langua ges.csharp:1963 99
| X-Tomcat-NG: microsoft.publi c.dotnet.langua ges.csharp
|
| I've got to believe this is a fairly common / classic problem, and I think
| I've even read an example somewhere in my education thus far, but I sure
| can't remember it.
|
| Suppose I want to store a list of first and last names read from a file.
I
| think somewhere I need an ArrayList. So I have a class that stores a
| private ArrayList.
|
| I want this class to be able to return the first name, the last name, or a
| "calculated " FullName... but I want to be able to set a property of this
| class of say Capitalization and have it affect the results of accessing
the
| names. I realize it's easy enough to have a class implement an indexer
that
| returns the proper element of say an ArrayList of structures, but I need
to
| modify each part of the structure upon it's access. That would be easy
| enough to do in the accessors in the structure, but the structure doesn't
| really know anything about the class's Capitalization property, and I
really
| want to avoid having the structure also hold a Capitalization property and
| having to go through the entire ArrayList every time the Class property is
| changed.
|
| I realize I could also code a GetLastName(int index) or something like
that
| in the class, but that seems a bit kludgey and wouldn't be as
| straightforward to the users of the class as I would hope to achieve.
What
| I'd like to achieve when using the class is something like..
|
| NamesList myNamesList = new NamesList();
| myNamesList.Rea dFromFile("blah blah.txt");
| myNamesList.Cap italization = NameCapitalizat ion.AllCaps;
| Console.WriteLi ne(NamesList[1].FirstName); // Output is "DAN"
| myNamesList.Cap italization = NameCapitalizat ion.ProperName;
| Console.WriteLi ne(NamesList[1].FirstName); // Output is "Dan"
|
| What's the magic ingredient I'm missing?
|
|
|

[Jon Skeet [C# MVP]]

Daniel Billingsley <db**********@N O.durcon.SPAAMM .com> wrote:

What I'd like to achieve when using the class is something like..

NamesList myNamesList = new NamesList();
myNamesList.Rea dFromFile("blah blah.txt");
myNamesList.Cap italization = NameCapitalizat ion.AllCaps;
Console.WriteLi ne(NamesList[1].FirstName); // Output is "DAN"
myNamesList.Cap italization = NameCapitalizat ion.ProperName;
Console.WriteLi ne(NamesList[1].FirstName); // Output is "Dan"

What's the magic ingredient I'm missing?

A few options:

1) Each name could have a reference to the NamesList, and interrogate
that as to which capitalisation style to use.

Pros: Works as per the above code.
Cons: Any name could only be a member of one list; you'd need the extra
reference for every element; the name would need to know about the list
(which you may not want).

2) You could change the code to:

Console.WriteLi ne (NamesList.Firs tName[1]) and make the FirstName
property always return an appropriate object with an "int" indexer
which then asks the list what kind of capitalisation to use, and then
gets the appropriate name.

Pros: The name element is unchanged; it's cheap in memory; there's no
real tie between a name and the list containing it.
Cons: You'd need to change the client code; it feels pretty ugly; the
implementation wouldn't be very nice.

3) You could make your indexer return a clone of the name (or an
encapsulated copy of the name reference), with an appropriate
capitalisation flag, rather than the actual name.

Pros: Pretty clean - same pros as option 2.
Cons: Creates more objects than you probably want.
These are pretty much the options presented in the other posts as well,
I think, apart from 2) which might be a "new" one.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Daniel Billingsley]

Thanks everyone for the replies.

Jon, I did think of a few of those, and like you mention, some of them seem
pretty kludgey to me.

In particular, while option #1 would probably work for this case, I feel
it's a bit constraining of future potential.

Option #2 would seem to work pretty well, even if it ain't real pretty as
you mention. I had hoped for something a bit more elegant. But I'm
wondering what the declaration of the FirstName property would look like - I
mean how do you declare a property to appear to work like an indexer, that
is called with [] instead of ()?

In the clone option, you say there would be a large number of objects
created, but wouldn't the life/scope of the clone be fairly short? I mean
technically it would only exist during the Console.WriteLi ne lifespan,
right? Or are you saying the GC works in such an opportunistic way that
they would sort of pile up?

All in all I think I like William's posted approach. For obvious reasons, I
did not want to iterate through the entire ArrayList and set a property on
each struct or person class every time the NamesList property is changed. I
think I understand William to argue that from an OO standpoint the Person
class or struct should really contain the capitalization logic. That was
my thinking, and it had me struggling for a solution. His posted code seems
like a good compromise to me.

"Jon Skeet [C# MVP]" <sk***@pobox.co m> wrote in message
news:MP******** *************** *@msnews.micros oft.com...

Daniel Billingsley <db**********@N O.durcon.SPAAMM .com> wrote:

What I'd like to achieve when using the class is something like..

NamesList myNamesList = new NamesList();
myNamesList.Rea dFromFile("blah blah.txt");
myNamesList.Cap italization = NameCapitalizat ion.AllCaps;
Console.WriteLi ne(NamesList[1].FirstName); // Output is "DAN"
myNamesList.Cap italization = NameCapitalizat ion.ProperName;
Console.WriteLi ne(NamesList[1].FirstName); // Output is "Dan"

What's the magic ingredient I'm missing?

A few options:

1) Each name could have a reference to the NamesList, and interrogate
that as to which capitalisation style to use.

Pros: Works as per the above code.
Cons: Any name could only be a member of one list; you'd need the extra
reference for every element; the name would need to know about the list
(which you may not want).

2) You could change the code to:

Console.WriteLi ne (NamesList.Firs tName[1]) and make the FirstName
property always return an appropriate object with an "int" indexer
which then asks the list what kind of capitalisation to use, and then
gets the appropriate name.

Pros: The name element is unchanged; it's cheap in memory; there's no
real tie between a name and the list containing it.
Cons: You'd need to change the client code; it feels pretty ugly; the
implementation wouldn't be very nice.

3) You could make your indexer return a clone of the name (or an
encapsulated copy of the name reference), with an appropriate
capitalisation flag, rather than the actual name.

Pros: Pretty clean - same pros as option 2.
Cons: Creates more objects than you probably want.
These are pretty much the options presented in the other posts as well,
I think, apart from 2) which might be a "new" one.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Daniel Billingsley]

I also thought this morning that I could probably make this work by using a
static field/property in the Person class, right? In a very limited and
controlled situation that would meet my needs, but I am also apprehensive
about the constraints that would put on future potential. For example, if I
had two NamesLists, each with its ArrayList of Person classes, then
effectively the capitalization would be the same for both NamesLists.
Right? That's exactly why static variables are so "dangerous" , isn't it?

[Jon Skeet [C# MVP]]

Daniel Billingsley <db**********@N O.durcon.SPAAMM .com> wrote:

Thanks everyone for the replies.

Jon, I did think of a few of those, and like you mention, some of them seem
pretty kludgey to me.

In particular, while option #1 would probably work for this case, I feel
it's a bit constraining of future potential.

Option #2 would seem to work pretty well, even if it ain't real pretty as
you mention. I had hoped for something a bit more elegant. But I'm
wondering what the declaration of the FirstName property would look like - I
mean how do you declare a property to appear to work like an indexer, that
is called with [] instead of ()?
You wouldn't - the property would have to return something which itself
had an indexer. And yes, that's nasty :(
In the clone option, you say there would be a large number of objects
created, but wouldn't the life/scope of the clone be fairly short?
Yup, so it's probably not a problem.
I mean
technically it would only exist during the Console.WriteLi ne lifespan,
right? Or are you saying the GC works in such an opportunistic way that
they would sort of pile up?
They'd pile up *very* temporarily.
All in all I think I like William's posted approach. For obvious reasons, I
did not want to iterate through the entire ArrayList and set a property on
each struct or person class every time the NamesList property is changed. I
think I understand William to argue that from an OO standpoint the Person
class or struct should really contain the capitalization logic. That was
my thinking, and it had me struggling for a solution. His posted code seems
like a good compromise to me.

Certainly the Person class itself doing the formatting would be OO
goodness.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

Daniel Billingsley <db**********@N O.durcon.SPAAMM .com> wrote:

I also thought this morning that I could probably make this work by using a
static field/property in the Person class, right?
Yes, although that's not very clean.
In a very limited and
controlled situation that would meet my needs, but I am also apprehensive
about the constraints that would put on future potential. For example, if I
had two NamesLists, each with its ArrayList of Person classes, then
effectively the capitalization would be the same for both NamesLists.
Right? That's exactly why static variables are so "dangerous" , isn't it?

Yup. You might also have a think about the nasty consequences of having
multiple threads doing stuff at the same time...

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too