<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>I've run out of ideas again</title><link>http://blogs.msdn.com/grantri/archive/2004/12/01/273265.aspx</link><description>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,</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: I've run out of ideas again</title><link>http://blogs.msdn.com/grantri/archive/2004/12/01/273265.aspx#273283</link><pubDate>Wed, 01 Dec 2004 21:12:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:273283</guid><dc:creator>Scott Sargent</dc:creator><description>I'd love to know more about the compiler.  If you've already blogged about this (or others have, my appologies) &lt;br&gt;&lt;br&gt;How about some cool things that the C# compiler can do that might not be commonly known?  For example C++ compilers by virtue of macros can do some really neat things to aid performance of in the code, recursive macros come to mind.  In C++ those may or may not be a good idea depending on the situation; but in regards to C# are there any compiler tricks that come to mind?  &lt;br&gt;&lt;br&gt;How much optimization does the C# compiler do, iirc the C++ compiler does more optimization of its il output.  But this is something i read/heard with the v1.0/1.1 versions.  Beyond new language features of C# what's new in the compiler for whidbey?  &lt;br&gt;&lt;br&gt;What are some interesting features that were considered and didn't make it into the compiler?  What might we see with the version beyond whidbey? </description></item><item><title>re: I've run out of ideas again</title><link>http://blogs.msdn.com/grantri/archive/2004/12/01/273265.aspx#273345</link><pubDate>Wed, 01 Dec 2004 22:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:273345</guid><dc:creator>Eric Wilson</dc:creator><description>I'm curious why the following is illegal:&lt;br&gt;&lt;br&gt;class A&lt;br&gt;{&lt;br&gt;   public static Foo()&lt;br&gt;   {&lt;br&gt;   }&lt;br&gt;}&lt;br&gt;&lt;br&gt;class B&lt;br&gt;{&lt;br&gt;   public DoStuff()&lt;br&gt;   {&lt;br&gt;      A myA;&lt;br&gt;      myA.Foo()   // &amp;lt;---This line blows up the compiler&lt;br&gt;    }&lt;br&gt;}&lt;br&gt;&lt;br&gt;I understand that this is illegal because the spec says so.  But is there any reason this is illegal in the first place?</description></item><item><title>re: I've run out of ideas again</title><link>http://blogs.msdn.com/grantri/archive/2004/12/01/273265.aspx#273755</link><pubDate>Thu, 02 Dec 2004 16:19:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:273755</guid><dc:creator>orangy</dc:creator><description>Why it is forbidden to derive from delegates? It could be feature activated by &amp;quot;advanced&amp;quot; compiler switch for experienced programmers. For example, I'd like to have WeakDelegate, which has a meaning &amp;quot;notify me while I'm alive&amp;quot; instead of current &amp;quot;notify and hold me&amp;quot;.</description></item><item><title>re: I've run out of ideas again</title><link>http://blogs.msdn.com/grantri/archive/2004/12/01/273265.aspx#273768</link><pubDate>Thu, 02 Dec 2004 16:44:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:273768</guid><dc:creator>Dmitriy Zaslavskiy</dc:creator><description>I cannot believe you ran out of ideas!&lt;br&gt;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?&lt;br&gt;</description></item><item><title>re: I've run out of ideas again</title><link>http://blogs.msdn.com/grantri/archive/2004/12/01/273265.aspx#273769</link><pubDate>Thu, 02 Dec 2004 16:42:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:273769</guid><dc:creator>Frank Hileman</dc:creator><description>Here are some ideas. This is not necessarily specific to 64-bit, but you seem to be working at the &amp;quot;bare metal&amp;quot; level.&lt;br&gt;&lt;br&gt;- 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.&lt;br&gt;&lt;br&gt;- Other basic optimization stuff. Why 64 bit might be better than 32, when. How the CLR will improve.</description></item><item><title>re: I've run out of ideas again</title><link>http://blogs.msdn.com/grantri/archive/2004/12/01/273265.aspx#273806</link><pubDate>Thu, 02 Dec 2004 17:26:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:273806</guid><dc:creator>Ryan Lamansky (Kardax)</dc:creator><description>Anything along the lines of &amp;quot;cool CLR stuff you might not know about coming in .NET 2.0&amp;quot; would be fun :)&lt;br&gt;&lt;br&gt;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.</description></item><item><title>re: I've run out of ideas again</title><link>http://blogs.msdn.com/grantri/archive/2004/12/01/273265.aspx#274119</link><pubDate>Fri, 03 Dec 2004 03:23:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:274119</guid><dc:creator>John Melville</dc:creator><description>I'd have to second the delegate question.&lt;br&gt;&lt;br&gt;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 &amp;quot;implicit&amp;quot; generic constraints, why is there no INumber interface.  (Make it hard to write generic numerical libraries.)&lt;br&gt;&lt;br&gt;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.</description></item><item><title>re: I've run out of ideas again</title><link>http://blogs.msdn.com/grantri/archive/2004/12/01/273265.aspx#278011</link><pubDate>Wed, 08 Dec 2004 02:41:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:278011</guid><dc:creator>Wes Haggard</dc:creator><description>I have a question for you. You may not be the right person to be asking this too but I will try anyways.&lt;br&gt;&lt;br&gt;A while back I posted &lt;a target="_new" href="http://weblogs.asp.net/whaggard/archive/2004/10/12/241476.aspx"&gt;http://weblogs.asp.net/whaggard/archive/2004/10/12/241476.aspx&lt;/a&gt;  about having a generic type inherit from Attribute. Do you know why this is prohibited in C#?&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;Wes</description></item><item><title>re: I've run out of ideas again</title><link>http://blogs.msdn.com/grantri/archive/2004/12/01/273265.aspx#279193</link><pubDate>Thu, 09 Dec 2004 22:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:279193</guid><dc:creator>Eric Wilson</dc:creator><description>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?</description></item></channel></rss>