« Longhorn News | Main | The Art of Thread Synchronization »

March 24, 2005


Samuel Jack

I see you added a comment to my suggestion on the Product Feedback Centre (http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=8211e737-4086-4854-9611-a91354b06741).

Did you vote for it?

Joe Duffy

Hey Wesner, it was great chatting for a bit the other night. If you'd like to discuss further, just drop me a line at joedu at microsoft dot com.

Thanks for pointing out the (a?) flaw in my weak delegate implementation. Glad to see Ian made the same mistake. ;) I didn't spend enough time thinking through the whole thing, and am a little embarassed I made such a fundamental misstep. Ah well. As I noted, this is certainly a feature on our wish list for future versions. (The correct implementation, that is.)

Lazy or unbound delegates in Whidbey can be used to alter the target of the delegate per invocation. At least you could early in Whidbey. Now I'm not so sure. The IL I cooked up for this seemingly doesn't work properly on the latest drop. But I did read the spec, so I don't think I imagined it. I'm following up with JoelPob on this--it may be that reflection is the best you get for now. But I hope not.

Apologies for the double dispatch disconnect. I am certainly familiar with the visitor pattern, but just didn't hook up the terminology with the idea in that context. It's used quite a bit in all of my compilers--my standard backend uses a visitor with double dispatch for visiting nodes. I reuse visitors both for rewriting ASTs, annotating them with type inferencing information, and spitting out code. If you have specific questions around the topic, let me know.

I myself am quite interested in radical ideas, especially when having to do with academia (a little too much for my own good no doubt). Haskell is my true love, although there are plenty of other great language to learn from, too. I really wish we had better support for continuations, coroutines, baked in support for closures and access to free variables (rather than every compiler hacking it), a static notion of identifying side-effects versus pure computation, among many other "old" ideas. There are some really interesting new things on the horizon that I'm particularly interested in, too.

Take care.

Lloyd Dupont

well you said it tooks you a while to know the subtle difference between Graphics.Save() & Graphics.BeginContainer() or that it tooks you a while (too) to learn how to overcome the limitations of GDI text rendering.

Well, well, well...
but what about providing some links to those who have the same problem?
hey! ;)

Eric Cosky

Yes please do share what you learned about Graphics.Save vs Graphics.BeginContainer :)

Thanks in advance,

Wesner Moise

See post in http://wesnerm.blogs.com/net_undocumented/2006/06/msdn_wiki_post.html

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Your Information

(Name is required. Email address will not be displayed with the comment.)