More late-bound invocation scenario notes

New and Notable 50

Sam Gentile's Blog — Sat, 24 Apr 2004 21:40:00 GMT

New and Notable 50

Sam Gentile's Blog — Sat, 24 Apr 2004 21:47:00 GMT

Items of interest pt11

Andrew Stopford's Weblog — Mon, 26 Apr 2004 23:24:00 GMT

re: More late-bound invocation scenario notes

Dmitriy Zaslavskiy — Mon, 03 May 2004 21:32:00 GMT

Joel,
I asked in few other places, but never got any answers.
Why can't CLR team add ability to set Target on a delegate?
This would allow for efficient implementation of known method / unknown object.

Thanks

re: More late-bound invocation scenario notes

Joel Pobar — Sun, 09 May 2004 20:31:00 GMT

Hi,

The main reason for not allowing the ability to set the target of a delegate after creation is because Delegates are immutable. Creating a delegate is straightforward, so changing the target of an existing delegate is not really compelling. There are scenarios where this kind of feature would end up breaking existing contracts (if you pass in a delegate to a component and the component uses it as a callback or event mechanism, and the creator may rely on that instance receiving that call).

Having said all that, we do have a compelling "relaxed" delegate story coming up for Whidbey. A few new features, a whole lot of fun. Perhaps I'll blog about it one of these days.

Back from Singapore Rotor Workshop

Joel Pobar's weblog — Mon, 21 Jun 2004 03:54:00 GMT

Back from Singapore Rotor Workshop

Joel Pobar's weblog — Mon, 21 Jun 2004 18:35:00 GMT

Back from Singapore Rotor Workshop (from: Joel Pobar)

Test .Text Blog — Tue, 22 Jun 2004 03:30:00 GMT

re: More late-bound invocation scenario notes

Alan Cyment — Mon, 19 Jul 2004 21:51:00 GMT

Hi Joel,

I'm currently developing a "message reifier" for MSIL. The main idea is to turn "message passing" (method calls - field accessing - etc) into first-class citizens (ie objects). I'm using RAIL to analyze a compiled assembly and I'm replacing every call/callvirt/calli with a couple of MSIL instructions that redirect flow to a "reifier" object, who should afterwards let the original flow keep its original way.
What do you think would be the best alternative for this scenario? I'm currently passing both the assembly & method name, doing a lookup of the method and using Invoke() to call it. Do you think this could be achieved using delegates?

TIA,
Alan

How to invoke a method with "out" parameter?

Ofer — Wed, 04 Aug 2004 12:08:00 GMT

How to invoke methods with an "out" parameter?

A MethodInfo of a static method with an out parameter had a parameter type as "GeneralTDS.MyDataTable&".
What does the "&" mean?

I'll appreciate if you can reply to true_9090 @ yahoo .com

Thanks.

More Clr stuff

Dinis Cruz @ Owasp .Net Project — Mon, 30 Jan 2006 14:55:28 GMT

Very,
Very interesting interview by Anders Hejlsberg (the lead C#
architect) with Bruce Eckel...