<?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>Strict Mode:  V1 Debug Tool V1 / V2 Best Practice</title><link>http://blogs.msdn.com/powershell/archive/2008/05/21/strict-mode.aspx</link><description>When we designed PowerShell we decided that we wanted to have Shell syntax and semantics because this is what was missing from the market and because it supports the ad hoc development practice that is so suited to the needs of administrators. We also</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>  WPF From PowerShell - Select-Grid</title><link>http://blogs.msdn.com/powershell/archive/2008/05/21/strict-mode.aspx#8528705</link><pubDate>Wed, 21 May 2008 19:49:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8528705</guid><dc:creator>  WPF From PowerShell - Select-Grid</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://HuddledMasses.org/wpf-from-powershell-select-grid/"&gt;http://HuddledMasses.org/wpf-from-powershell-select-grid/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Strict Mode:  V1 Debug Tool V1 / V2 Best Practice</title><link>http://blogs.msdn.com/powershell/archive/2008/05/21/strict-mode.aspx#8532468</link><pubDate>Thu, 22 May 2008 20:02:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8532468</guid><dc:creator>Keith Hill</dc:creator><description>&lt;p&gt;I really like the increased functionality however I'm curious why you didn't go with something like #require strict -v 2. &amp;nbsp;Was it primarily to support the global/shell scope i.e. interactive usage?&lt;/p&gt;</description></item><item><title>re: Strict Mode:  V1 Debug Tool V1 / V2 Best Practice</title><link>http://blogs.msdn.com/powershell/archive/2008/05/21/strict-mode.aspx#8532548</link><pubDate>Thu, 22 May 2008 20:13:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8532548</guid><dc:creator>Jared Parsons</dc:creator><description>&lt;p&gt;This is a really exciting feature. &amp;nbsp;I think the relaxed semantics of PowerShell are very powerful for most scripting. &amp;nbsp;But for my larger script sets/programs I need a bit more checking and this will help out tremendously. &amp;nbsp;&lt;/p&gt;</description></item><item><title>re: Strict Mode:  V1 Debug Tool V1 / V2 Best Practice</title><link>http://blogs.msdn.com/powershell/archive/2008/05/21/strict-mode.aspx#8570346</link><pubDate>Tue, 03 Jun 2008 00:44:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8570346</guid><dc:creator>bsdz</dc:creator><description>&lt;p&gt;A great addition. Very similar to Perl's &amp;quot;use strict&amp;quot;. I feel that you guys are certainly picking the better elements of many different languages.&lt;/p&gt;</description></item></channel></rss>