<?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>Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx</link><description>I've been recently puzzling out a strategy for presenting the two mechanisms supporting parameterized types available to the C++/CLI programmer: she can use either the template mechanism adapted for use with CLI types, or the CLI generic mechanism. This</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#209814</link><pubDate>Fri, 06 Aug 2004 13:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:209814</guid><dc:creator>GO DAWGS</dc:creator><description>You seem to be more than a little bitter about being excluded from the design of generics. I suspect this is systematic in the C++ community as you are pretty much getting owned by .net and C#. Why don't you just make the switch? I did, and have never looked back.&lt;br&gt;</description></item><item><title>re: Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#209857</link><pubDate>Fri, 06 Aug 2004 14:36:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:209857</guid><dc:creator>stan lippman</dc:creator><description>i don't mean to come across as bitter. i actually spent a long time -- well, about a year -- using C#. it was at the time the only viable window into .net, which is what interests me more than any particular language. my goal, if you will, when i joined microsoft, was to insure that c++ became a viable .net language -- and that has always meant being somewhat obnoxious, which of course is not my essential nature :-)&lt;br&gt;&lt;br&gt;and i believe this has happened -- C++ is imo a better window into .net that any other language -- however, it is only a window, and the work is uneven at best. but the effort is very satisfying and i suspect surprised many people who had written c++ off -- just as the java community did back in the mid-1990s. &lt;br&gt;&lt;br&gt;personally, i think you are the poorer for having never looked back -- and i would argue that you diminish your toolbox into .net by holding to that view.&lt;br&gt;&lt;br&gt;but, the main point is, there is nothing to be bitter about; this is how things work. one just has to focus and keep what's important in mind, and not just throw off the past because things currently aren't going well. one can alternatively try to make things better -- and i think we have done that with visual c++ 2005, which is now available and begins to compete. how could i be bitter about that? so, if i came across that way, i did not mean to, and i hope this response goes a small way in offsetting that impression ...&lt;br&gt;&lt;br&gt;stan&lt;br&gt;&lt;br&gt;&lt;br&gt;</description></item><item><title>re: Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#210237</link><pubDate>Fri, 06 Aug 2004 22:17:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:210237</guid><dc:creator>GO DAWGS</dc:creator><description>Sorry, I was just mad 'cause my job sucks. I was trying to joke but it didn't really work. Anyway, thanks for the great blog entry.&lt;br&gt;</description></item><item><title>re: Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#210351</link><pubDate>Sat, 07 Aug 2004 03:28:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:210351</guid><dc:creator>Nish</dc:creator><description>I personally believe that while C++/CLI might appear (initially) to have a tougher syntax than languages like C#, eventually it will be the #1 language for core-programmers to target .NET.&lt;br&gt;&lt;br&gt;Of course it's just my opinion here, not sure how much that counts.</description></item><item><title>re: Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#210946</link><pubDate>Sun, 08 Aug 2004 21:20:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:210946</guid><dc:creator>LDC</dc:creator><description>I think C++ is too complex now...faint!</description></item><item><title>re: Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#211074</link><pubDate>Mon, 09 Aug 2004 05:10:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:211074</guid><dc:creator>stan lippman</dc:creator><description>well, these two comments together fairly represent a continuum ... this is why there are multiple languages available ... to serve each sensibility. cheers.</description></item><item><title>Complexity of templates</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#211231</link><pubDate>Mon, 09 Aug 2004 12:37:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:211231</guid><dc:creator>Nemanja Trifunovic</dc:creator><description>I would just like to comment on complexity of templates as a reason to use generics instead.&lt;br&gt;&lt;br&gt;IMO, there are two distinct groups of people that use templates: those who write template libraries, and those who use template libraries.&lt;br&gt;&lt;br&gt;Now, writing template libraries is tough. Templates used in this manner are complex, hard to debug, and often library writers use horrible hacks to work around some limitations of templates. However, only a small minority of C++ programmers ever gets a chance to be in that roles, and those who do are masters like Alexandrescu, Stepanov, Maddock, etc - they are not afraid of &amp;quot;complexities&amp;quot;.&lt;br&gt;&lt;br&gt;On the other hand, template library can (and indeed, often do) expose clean, logical, easy to use interface to application programmers. When you use e.g. Loki you don't really meet any of those &amp;quot;terribly complex&amp;quot; aspects of template programming - the burden was on the author of the library.&lt;br&gt;&lt;br&gt;Therefore, I would say that all this talk about &amp;quot;complex templates&amp;quot; and &amp;quot;simple generics&amp;quot; is in practice a non-issue for the vast majority of programmers. The only &amp;quot;real-workld&amp;quot; problem with using template libraries I can think of is not-quite-readable compile error messages. It seems that generics are better in this regard. As for two phase name lookup and other subtleties, only a small number of people ever need to care about them.</description></item><item><title>re: Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#211580</link><pubDate>Tue, 10 Aug 2004 03:11:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:211580</guid><dc:creator>stan lippman</dc:creator><description>thank you for writing. </description></item><item><title>re: Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#211655</link><pubDate>Tue, 10 Aug 2004 05:34:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:211655</guid><dc:creator>LDC</dc:creator><description>But when C++ is easier to use, there will be more people to write  libraries, isn't it?</description></item><item><title>re: Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#211828</link><pubDate>Tue, 10 Aug 2004 12:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:211828</guid><dc:creator>Nemanja Trifunovic</dc:creator><description>Not if that &amp;quot;ease of use&amp;quot; comes at the expense of power and flexibility. With generics, it is just not possible to make libraries like Loki, MTL, most Boost libraries...&lt;br&gt;&lt;br&gt;Generics are great for making type-safe collections, but that's (almost) it. That is the price for its &amp;quot;simplicity&amp;quot;.</description></item><item><title>re: Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#212151</link><pubDate>Tue, 10 Aug 2004 19:20:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:212151</guid><dc:creator>stan lippman</dc:creator><description>well, i don't think we have enough experience with generics to be so dismissive. the real benefit of generics right now, however, are (a) MSIL/meta-data support, (b) cross-assembly visibility [templates are internal to an assembly], and, of course, (c) cross-language visibility. </description></item><item><title>Blog link of the week 32</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#220392</link><pubDate>Wed, 25 Aug 2004 18:32:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:220392</guid><dc:creator>Daniel Moth</dc:creator><description>&lt;a target="_new" href="http://www.zen13120.zen.co.uk/Blog/2004/08/blog-link-of-week-32-was-mistakenly-33.html"&gt;http://www.zen13120.zen.co.uk/Blog/2004/08/blog-link-of-week-32-was-mistakenly-33.html&lt;/a&gt;</description></item><item><title>Generics </title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#253098</link><pubDate>Sat, 06 Nov 2004 01:28:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:253098</guid><dc:creator>Being Scott Densmore</dc:creator><description /></item><item><title>D?velopper en C++ ? - Page 4 | hilpers</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#9367834</link><pubDate>Thu, 22 Jan 2009 17:22:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9367834</guid><dc:creator>D?velopper en C++ ? - Page 4 | hilpers</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.hilpers.fr/397421-developper-en-c/4"&gt;http://www.hilpers.fr/397421-developper-en-c/4&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>
		Topics about Tour-eiffel		 | 		  Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#9559569</link><pubDate>Tue, 21 Apr 2009 18:54:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9559569</guid><dc:creator>
		Topics about Tour-eiffel		 | 		  Why C++/CLI Supports both Templates for CLI Types and the CLI Generic Mechanism</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://tour-eiffel.linkedz.info/2004/08/05/why-ccli-supports-both-templates-for-cli-types-and-the-cli-generic-mechanism/"&gt;http://tour-eiffel.linkedz.info/2004/08/05/why-ccli-supports-both-templates-for-cli-types-and-the-cli-generic-mechanism/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Stan Lippman s BLog Why C CLI Supports both Templates for CLI Types | Outdoor Decor</title><link>http://blogs.msdn.com/slippman/archive/2004/08/05/209606.aspx#9779132</link><pubDate>Fri, 19 Jun 2009 07:30:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9779132</guid><dc:creator> Stan Lippman s BLog Why C CLI Supports both Templates for CLI Types | Outdoor Decor</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://outdoordecoration.info/story.php?id=3366"&gt;http://outdoordecoration.info/story.php?id=3366&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>