C#

using System;

    class String
    {
        public string RemoveFirst(string num)
        {
            //num = num.Remove(num);
            string toReturn = num.Remove(0, 1);
            return toReturn;
            //Console.WriteLine("Hackz0red!");
        }
    }

    class ExtMethodDemo
    {
        static void Main(string[] args)
        {
            String r1 = new String();
            string r2 = r1.RemoveFirst("12345");
            Console.WriteLine(r2);
            Console.ReadLine();
        }
    }

public static class ExtMethods
{
    public static string RemoveFirst(this string str)
    {
        return str.Remove(0,1);
    }
}
  class ExtMethodDemo
    {
        static void Main(string[] args)
        {
            string r1 = "12345".RemoveFirst();
            Console.WriteLine(r1);
            Console.ReadLine();
        }
    }

betonglasermur.FeedDwarf(pur_is, 17);
ProcessStartupInfo.AintNotCreateNoWindow = (false && !true) != (true || false) ? false == true ? true : false : (true != false && false);

buchstaben wrote:

In effect, extension methods make it possible

PIEBALDconsult wrote:

buchstaben wrote:
In effect, extension methods make it possible


make it appear possible, when in fact it isn't.

George_George wrote:

I understand there is no need to call Dispose explicitly when dealing with StreamReader/StreamWriter object instances

using (StreamReader sr = new StreamReader(someStream))
{
  ...
}

George_George wrote:

What is the benefit?

George_George wrote:

when the Http Service stops (process stops or terminations), all resources like native handle wrapped by StreamReader could be released automatically.

What is the benefit of using "using" statement?

using(Stream str = new FileStream(..))
{
   // Use str here
}

Stream str = null;
try
{
   str = new FileStream(..);
}
finally
{
   if(str != null)
     ((IDisposable)str).Dispose();
}

George_George wrote:

In the C# compiler expanded code, no catch block? Just a finally block?