Design and Architecture

Netblue wrote:

VisualSVN

CodingYoshi wrote:

However, I also know that all objects are passed by reference.

Dim values(10) As Integer

int[] values = new int[10];

using System;
class Program
{
    static void Main()
    {
        int[] values = { 1, 2, 3 };
        TestMethod(values);
        Console.WriteLine("{0}, {1}, {2}", values[0], values[1], values[2]);
    }

    static void TestMethod(int[] values)
    {
        int[] newArray = new int[] { 4, 5, 6 };
        values = newArray;
    }
}

static void TestMethod(int[] values)
{
    values[0] = 4;
    values[1] = 5;
    values[2] = 6;
}

CodingYoshi wrote:

when arguments are passed byVal it hinders performance since a copy needs to be made

CodingYoshi wrote:

If a method only needs to read an argument but does not need to modify it, does it make sense to send it byref?

RichardGrimmer wrote:

Now I've moved into a more "relaxed" environment, but the code is basically a big morass of procedural code in an object oriented dress - with inheritance implemented using copy and paste lol....

RichardGrimmer wrote:

so unless I'm expecting my class to have many clients, there's not really much point in going down the interface route?

I'm clearly missing something here, just not sure what lol!

RichardGrimmer wrote:

are c# interfaces immutable in the same way that COM interfaces were

led mike wrote:

First, COM is not Object Oriented Design and there is not generally any reason to compare COM to OOD. Also I am not sure what you mean by immutable

Pete O'Hanlon wrote:

so changing the interface resulted in the VTable being incorrect

led mike wrote:

My best guess is that you mean, can you modify an interface, build and distribute the assembly without breaking existing code.