C#

<br />
private void button1_Click(object sender, EventArgs e)<br />
        {<br />
            for (int g = 0; g < 10; g++)<br />
            {<br />
                string[] namesArray = new string[3] { "Martin", "Was", "Here" };<br />
<br />
                for (int i = 0; i < namesArray.Length; i++)<br />
                {<br />
                    ListViewItem lvi = new ListViewItem(namesArray[0]);<br />
                    lvi.SubItems.Add(namesArray[1]);<br />
                    lvi.SubItems.Add(namesArray[2]);<br />
<br />
                    lvi.BackColor = Color.FromArgb(Convert.ToInt32("58996"));<br />
                    listView1.Items.Add(lvi);<br />
                }<br />
            }               <br />
        }<br />

Luc Pattyn wrote:

the way I understood it, keyboard and mouse input basically go to the app, Application.Run(new Form1()) make them go to your instance of Form1, and from there they get dispatched to the Form and its content (thru Controls property).

Luc Pattyn wrote:

BTW: there is a free implementation of .NET available under ssCLI or shared source CLI.

System.Text.StringBuilder sb = new System.Text.StringBuilder ( "ABCD" ) ;
sb.Insert ( 0 , "BLABLA" , 1 ) ;

shyagam wrote:

It is well known that when a string's length is already known or can be easily calculated, it is best to use StringBuilder instead of string.

shyagam wrote:

The reason I think it's the same is because to my understanding, when hardcoding the "BLABLA" string, memory is allocated for it anyway.

string s="";
foreach (char c in "abcdefghijklmnopqrstuvwxyz") s=s+c;
Console.WriteLine(s);

StringBuilder sb=new StringBuilder(100);  // large enough
foreach (char c in "abcdefghijklmnopqrstuvwxyz") sb.Append(c);
string s=sb.ToString();
Console.WriteLine(s);

haseebbutt007 wrote:

the windows installer automatically copy that DLL in System and System32 Folders

Well, actually, it doesn't hang. It just takes a really really long time, and you haven't waited long enough for it to finish. One of the pitfalls with regular expression is that you can write expressions which don't perform very well. In particular, you can end up with expressions whose search time grows exponentially with the length of the search string. I get bugs reporting that Regex hangs about once a month, and it always turns out to be an exponentially slow expression. Here's a simplified example of one of them:

([a-z]+)*=

There are two things interesting about this expression. First, notice that it has two quantifiers nested within each other. The inner one is the + quantifier for the character class, and the outer one is the *. Second, it has a character (the equals char) that must be matched at the end of the result. In English terms, this expression can be explained as

1. match any character a-z, one or more times
2. match step #1 zero or more times
3. match an equals

What will happen is that Regex will breeze through step 1 and 2 only to find that it can't match in step 3. That forces it to backtrack and try to match the first two steps differently. The trouble is that there are a lot of different ways that steps 1 and 2 can match, and Regex needs to try every single one before it can determine that the expression does not match the string.