Combining Arrays?

Quote:

---

Originally Posted by Amerikon

There's a lot to be gained by pulling back the curtain so you can understand why calling List.AddRange() works.

---

That is true, and for learning valuable, but IMHO has no place in any "real" program (even one written by a hobbiest).

If you REALLY want to know how things work, write some assembly code that properly manages a quad core, pipelined, dual level chached processor...

btw: I know one person who does exactly that. He is considered the leading expert in super high performance realtime (but his passion is writing games :) ). The problem is that NOBODY but him can do even the slightest maintenance on his code. Often changing a single instruction will completely break the code. So we keep him in a VERY small box, and make sure his code is used only where it is ABSOLUTELY needed.

First off, there is no way you're comparing combining arrays with socket communication and web services. Combining arrays is about as basic a programming task as you can imagine. It was also pretty clear from the original post, that the poster didn't know how to combine two arrays. Why am I so out of line for suggesting that he's better off having seen an example of how it's done instead of just throwing some
First off, there is no way you're comparing combining arrays with socket communication and web services. Combining arrays is about as basic a programming task as you can imagine. It was also pretty clear from the original post, that the poster didn't know how to combine two arrays. Why am I so out of line for suggesting that he's better off having seen an example of how it's done instead of just throwing some built-in functionality at him? If the original poster looked at my example and understood how it works he can now combine arrays in pretty much any language that supports arrays. If all he knows is List.AddRange() he can only combine arrays in .NET, and additionally comes away with the idea that in order to combine two arrays you have to use a List object. Which is why my first post said "here's how you combine arrays but using the List object is easier".
Second, the analogy driver:car :: programmer:program doesn't work. A driver is far more like a user than a programmer. When a programmer writes code, if that code breaks, the programmer has to fix it. He has to know enough about what's going on "under the hood" so that he can diagnose and solve the problem. There is a certain set of fundamental skills (including how arrays are manipulated) that you have to know if you want to program. Otherwise we might as well just hand out CS degrees with copies of the .NET SDK docs.

That tongue-out smiley is supposed to be a colon followed by a p. programmer : program.

In the U.S. there is a Yamaha motorcycle commercial that plays where kids are shown trying to start their dirtbikes. Yamaha is trying to sell their new line of electric start dirtbikes. They show them kicking and kicking and then the dads come up and try to start them. While this is going on, in the background you can hear kids sing, "I wanna ride, I wanna ride, I just wanna ride."

So for this post, maybe "I just wanna code" is apt?

Sometimes you just need to complete the task at hand and get on with it.

If I hire a beginning programmer, I expect the programmer to understand the basics. However, I expect the programmer to move beyond the basics and leverage what the environment offers.

Too often beginning programmers get caught up into manually coding such tasks. In C++, it was common to see yet another linked list implementation or a string class (rather than use stl). [If I see another homegrown C++ string class, I think I'm going to hurl]

C# is no different. Understand it, and then move on.

Code:

---

class String
{
public:
......
}

---

:D :D :D :wave:

If you're too young to start your dirt-bike, maybe you shouldn't be riding. :-)

perhaps the answer should have been:


Use a List<string>.AddRange for each of the arrays sent back from get files, and download reflector on your own time to learn how add range works.

This thread could go on and on, but I just want to say that although I'm a KTM fan, Yamaha makes some pretty dang good dirt bikes.