C# Simple Array Help

Question

1.80/5 (2 votes)

See more:

I am relatively new to C# so I am kind of stuck on some code but I feel the fix is kind of simple. If anyone could help fix the code that would help me a lot.

C#

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace ConsoleApplication13
{
    class Program
    {
        static void Main(string[] args)
        {
            arrayList mylist = new arrayList(4);
            mylist.addFirst('a');
            mylist.addFirst('b');
            mylist.addFirst('c');
            mylist.addFirst('d');
            try
            {
                mylist.addFirst('e');
            }
            catch
            {
            }
        }
    }
}

C#

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Collections;

namespace ConsoleApplication13
{
        public arrayList(int v)
        {
            mylist = new char(v);
            size = 0;
        }

        public bool isEmpty()
        {
            bool rvalue = false;
            if (size == 0)
            (
                rvalue = true;
            )

            return rvalue;
        }

        public void addFirst(char c)
        {
            if (size == mylist.Length)
                throw new Exception
        }

    
}

Posted 8-Dec-13 0:14am

Member 10452381

Updated 8-Dec-13 12:53pm

Sergey Alexandrovich Kryukov

v2

Add a Solution

Comments

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ) 8-Dec-13 6:40am

So what is the problem here?

Sergey Alexandrovich Kryukov 8-Dec-13 19:27pm

Don't use ArrayList, it's obsolete, superseded by System.Collections.Generic.List<>
—SA

gggustafson 8-Dec-13 21:14pm

I don't think ArrayList has been supersceded at all. It's just another tool in the C# programmer's toolbox.

Sergey Alexandrovich Kryukov 8-Dec-13 21:52pm

What you think is not true, not at all. There is nothing "another" in it. It wasn't formally marked obsolete only because there is nothing wrong with keeping it in legacy code thus keeping compatibility. There absolutely no sense in using this type in development. Doing it is less safe compared to equivalent System.Collections.Generic.List<> which does not require potentially dangerous typecast.
—SA

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

BillWoodruff · Answer 1 · 2013-12-08T00:43:00

Solution 1

Well, you could make the code simpler:

// required
using System;
using System.Collections;

// somewhere in a method ...

ArrayList aList = new ArrayList();
aList.AddRange(new string[] {"a","b","c","d","e"});
aList.Reverse();

But, is that really what you are after here ?

Posted 8-Dec-13 0:43am

BillWoodruff

OriginalGriff · Answer 2 · 2013-12-08T00:46:00

Um.
You can't do that: the second code sample has no class declaration, so what you are trying to do is declare the constructor and two methods as global methods - which C# does not have (if a "global constructor" made any sense anyway, which it doesn't).

Try adding the class declarations round it:

C#

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Collections;

namespace ConsoleApplication13
{
    public class arrayList
    {
        public arrayList(int v)
        {
            mylist = new char(v);
            size = 0;
        }

        public bool isEmpty()
        {
            bool rvalue = false;
            if (size == 0)
            (
                rvalue = true;
            )

            return rvalue;
        }

        public void addFirst(char c)
        {
            if (size == mylist.Length)
                throw new Exception
        }
    }
}

That should fix it.