<?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>The Least a C# Programmer Needs to Know about F# Part II--Modules</title><link>http://blogs.msdn.com/jomo_fisher/archive/2007/10/23/the-least-a-c-programmer-needs-to-know-about-f-part-ii-modules.aspx</link><description>Jomo Fisher--Many languages, especially those in the OO vein, require an outermost class to put code in. Usually, good practice requires an enclosing namespace as well. F# allows functions and even function calls in the outermost scope. Here is the minimal</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: The Least a C# Programmer Needs to Know about F# Part II--Modules</title><link>http://blogs.msdn.com/jomo_fisher/archive/2007/10/23/the-least-a-c-programmer-needs-to-know-about-f-part-ii-modules.aspx#5644152</link><pubDate>Wed, 24 Oct 2007 11:18:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5644152</guid><dc:creator>Robert Pickering</dc:creator><description>&lt;p&gt;“F# makes this style of API a first-class citizen: the Module.”&lt;/p&gt;
&lt;p&gt;A big +1 to that. I think having modules as well as classes is only a small shift in thinking but it’s an important one. The C# model of OO seem designed to make you think everything should be class, that is every part of a program should be modeled as something that can have multiple instances. For me, this simply isn’t true there are lots of places where having modules are very useful, the File/Directory/Path static classes from System.IO you high light are great examples of this. Sure let’s not throw out the baby with the bath water there are still lots of places where classes are useful, but let’s not assume classes are simply better than modules nor feel guilty about having modules/static classes in our programs.&lt;/p&gt;</description></item><item><title>Books on F#</title><link>http://blogs.msdn.com/jomo_fisher/archive/2007/10/23/the-least-a-c-programmer-needs-to-know-about-f-part-ii-modules.aspx#5802002</link><pubDate>Wed, 31 Oct 2007 20:58:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5802002</guid><dc:creator>Walter Stiers - Academic Relations Team (BeLux)</dc:creator><description>&lt;p&gt;Expert F# is about practical programming in a beautiful language that puts the power and elegance of&lt;/p&gt;
</description></item><item><title>Books on F#</title><link>http://blogs.msdn.com/jomo_fisher/archive/2007/10/23/the-least-a-c-programmer-needs-to-know-about-f-part-ii-modules.aspx#5802041</link><pubDate>Wed, 31 Oct 2007 21:02:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5802041</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;Expert F# is about practical programming in a beautiful language that puts the power and elegance of&lt;/p&gt;
</description></item></channel></rss>