Welcome to the Lounge

Yortw wrote:

8. Fix for the (very rare) bug caused by compiler optimisations on the String.IsNullOrEmpty function.

Anastasiosyal wrote:

3. Some Duck-typing

Member 3976638 wrote:

A couple of things I would like is better control over memory. The automatic garbage collection is nice and I understand that it's usualy better just to let it be so it can collect when needed, but in some cases I know the memory can and must be freed like when processing a large import file. Also I would like to be able to "Destroy" an object in certain situations. By that I mean to have one method that can nullify all refrences to a particualar object.

public int,int MinMax(int[] numbers)
{
   int min, max;
   // Code to calculate min/max
   min=whatever
   max=whatever
   return min, max;
}

public MinMax(int[] numbers, out int min, out int max)
{   
   // Code to calculate min/max
   min=whatever
   max=whatever
}

int min, max;
[min,max] = MinMax(new [] {1,2,3});

int min, max;
MinMax(new [] {1,2,3}, out min, out max);

public int A
{
    get
    {
        CanReadProperty(PropertyNames.A, true);
        return m_a;
    }
    set
    {
        CanWriteProperty(PropertyNames.A, true);
        if (!m_a.Equals(value))
        {
            m_a = value;
            PropertyHasChanged(PropertyNames.A);
        }
    }
}

public int A { get; set; from CslaProperty }

public string A
{
    get;
    set
    {
        if (value == null)
            value = "";
        @templateBase = value;
    }
}