Welcome to the Lounge

BobJanova wrote:

There's actually no reason why you can't have vtable entries for static methods

BobJanova wrote:

You just have to choose a different way of determining the type that should get dispatched, instead of using the instance's dynamic type,

BobJanova wrote:

the declaration type of the method which was originally called.

public static class BaseService {
 public static void LoadData() {
  Console.WriteLine(GetDataSource());
 } 

 protected virtual static string GetDataSource();
}

public static class FileService : BaseService {
 protected override static string GetDataSource() { return "file.dat"; }
}

public static class DatabaseService : BaseService {
 protected override static string GetDataSource() { return "database"; }
}

void Run() {
 DatabaseService.LoadData();
 FileService.LoadData();
}

void Run(Class<BaseService> service) {
 service.LoadData();
}

harold aptroot wrote:

no vptr

BobJanova wrote:

static inheritance (i.e. static virtual in C# speak), and that's a really useful concept that is missing in C#

OriginalGriff wrote:

That means I don't get "fixated" on "this must be why" and my subconscious is free to "bing" me and say "Try this, not that".

Quote:

I waste time on a bomb