I've run out of ideas again

  • Article

In case you haven't noticed, I've run out of ideas to write about.  I'm sure there's still a few things I know that I haven't explained, btu I can't remember them...

If you've been dying to know something about the C# compiler, ALink, CLR file formats, 64-bit JITs, please ask,a nd I'll see what I can do.

--Grant

Comments

  • Anonymous
    December 01, 2004
    The comment has been removed
  • Anonymous
    December 01, 2004
    The comment has been removed
  • Anonymous
    December 02, 2004
    Why it is forbidden to derive from delegates? It could be feature activated by "advanced" compiler switch for experienced programmers. For example, I'd like to have WeakDelegate, which has a meaning "notify me while I'm alive" instead of current "notify and hold me".
  • Anonymous
    December 02, 2004
    Here are some ideas. This is not necessarily specific to 64-bit, but you seem to be working at the "bare metal" level.

    - Currently struct temporaries, often produced by operator overloads, are not optimzied. Maybe discuss why this is important and how/when it will be fixed. I know why it is important, but others may not. I bring this up because 64-bit is touted for numerical applicaitons, but the struct problem kind of kills perf in .NET applications.

    - Other basic optimization stuff. Why 64 bit might be better than 32, when. How the CLR will improve.
  • Anonymous
    December 02, 2004
    I cannot believe you ran out of ideas!
    Could you please comment on inlining on 64bit platform. Could you talk about inlining with generics. Idiom where x86 code works in reasonable time and 64-bit code will cost unexpectedly much more? Memory models?
  • Anonymous
    December 02, 2004
    Anything along the lines of "cool CLR stuff you might not know about coming in .NET 2.0" would be fun :)

    I have to second Frank's suggestion about why/when 64 bit might be better than 32. There certainly has been a lot discussion about the disadvantages of 64-bit, a switch to the positive points (besides the obvious larger memory capacity) would be very interesting reading.
  • Anonymous
    December 02, 2004
    I'd have to second the delegate question.

    I am also very interested in some of the restrictions on generic types. i.e why can't a generic inherit from its parameter, why can't we use "implicit" generic constraints, why is there no INumber interface. (Make it hard to write generic numerical libraries.)

    Generics seem to really answer the freshman CS collections problems while missing some of the more expressive power of C++ templates. I am sure there were good reasons for those restrictions, I would just be curious as to what they were.
  • Anonymous
    December 07, 2004
    I have a question for you. You may not be the right person to be asking this too but I will try anyways.

    A while back I posted http://weblogs.asp.net/whaggard/archive/2004/10/12/241476.aspx about having a generic type inherit from Attribute. Do you know why this is prohibited in C#?

    Thanks,
    Wes
  • Anonymous
    December 09, 2004
    Could you do a post on what the settings on the Advanced Tab in Visual Studio.Net for C# projects are for and when you should use them?