Freigeben über

The Future of C#, Part Four: Yet More Video

  • Artikel

Mads, Chris, Sam and me on Channel Nine. Enjoy.

Comments

  • Anonymous
    November 02, 2008
    The comment has been removed

  • Anonymous
    November 02, 2008
    I'll probably use the dynamic feature and contra/covariance, but the rest is beyond what I usually do. It's great to know static and dynamic worlds are truly combined. I can't wait to call DirectShow objects with automatic interoping. Am I right? Will that work? I'd love to see a DirectShow example...

  • Anonymous
    November 02, 2008
    The comment has been removed

  • Anonymous
    November 03, 2008
    The comment has been removed

  • Anonymous
    November 03, 2008
    Oh dear, I just realised I was talking about the same thing peted was. I should read better before I post; sorry for that.

  • Anonymous
    November 03, 2008
    Welcome to the 47th Community Convergence. We had a very successful trip to PDC this year. In this post

  • Anonymous
    November 10, 2008
    @configurator: Yes, I understand the stated behavior.  But I don't understand yet why that stated behavior is consistent with a) using the same compiler code, and b) what's been said elsewhere about how this stuff works. As another example, check out Sam Ng's latest blog post: http://blogs.msdn.com/samng/archive/2008/11/09/dynamic-in-c-iii-a-slight-twist.aspx In it, he writes "dynamic binding behaves exactly as it would at static compile time, with the exception that the type used in place of the dynamic objects (arguments or receiver) is the runtime determined type instead of the compile time determined one. This means that for all arguments not statically typed dynamic, the compile time types will be used, regardless of their runtime types" Taking that statement at face value, I would expect our example above to call the Method(object) overload, not the Method(Int32) overload.  After all, the only thing the "dynamic" type should introduce is run-time determination of the method group to use; the overload resolution should be done based on the static typing of the argument, which is "object". Basically, I feel like we're seeing contradictory statements regarding the expected behavior of overload resolution with dynamic types.  While I feel like the "use all static information available" approach is the most predictable and least surprising, I wouldn't object to using run-time type information even for elements that have known compile-time type information if that's what the C# designers feel is the best approach. But right now I think I'm being told two mutually exclusive behaviors will both be implemented.  That's logically impossible, and I'd like someone to straighten me out.  :)

  • Anonymous
    December 23, 2008
    Very good resources for the coming version... Sam Ng Dynamic in C# Part One Dynamic in C# Part Two Chris