<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.oehive.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>The OpenEdge Hive - contributed rules</title>
 <link>http://www.oehive.org/taxonomy/term/462/0</link>
 <description></description>
 <language>oehive</language>
<item>
 <title>forwardparams</title>
 <link>http://www.oehive.org/prolint/rules/forwardparams</link>
 <description>&lt;h1&gt;parameters in function don&#039;t match with forward declaration&lt;/h1&gt;
&lt;p&gt;Rule &quot;forwardparams&quot; gives this warning when it finds that a function implementation has different parameters than its forward declaration.&lt;br /&gt;
For example:&lt;/p&gt;
&lt;pre&gt;
function myfunction returns logical(input something as character) forward.

function myfunction returns logical:
    if something&amp;gt;&quot;&quot; then 
       return true.
    else 
       return false.
end function.
&lt;/pre&gt;&lt;p&gt;
&lt;strong&gt;Why&lt;/strong&gt;&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/prolint&quot; class=&quot;og_links&quot;&gt;Prolint&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://www.oehive.org/prolint/rules/forwardparams&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.oehive.org/prolint/rules/forwardparams#comments</comments>
 <category domain="http://www.oehive.org/taxonomy/term/462">contributed rules</category>
 <group domain="http://www.oehive.org/prolint">Prolint</group>
 <pubDate>Wed, 04 Mar 2009 22:46:51 +0000</pubDate>
 <dc:creator>jurjen</dc:creator>
 <guid isPermaLink="false">1434 at http://www.oehive.org</guid>
</item>
<item>
 <title>fortranoper</title>
 <link>http://www.oehive.org/prolint/rules/fortranoper</link>
 <description>&lt;p&gt;Rule fortranoper searches for the use of Fortran-style operators like:&lt;br /&gt;
EQ, GT, LT, GE, LE, NE (for =, &amp;gt;, &amp;lt;, &amp;gt;=, &amp;lt;=, &amp;lt;&amp;gt;).&lt;/p&gt;
&lt;p&gt;I know some people may like this or are used to this, but others don&#039;t.&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/prolint&quot; class=&quot;og_links&quot;&gt;Prolint&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description>
 <comments>http://www.oehive.org/prolint/rules/fortranoper#comments</comments>
 <category domain="http://www.oehive.org/taxonomy/term/462">contributed rules</category>
 <group domain="http://www.oehive.org/prolint">Prolint</group>
 <pubDate>Wed, 11 Feb 2009 21:09:30 +0000</pubDate>
 <dc:creator>Niek</dc:creator>
 <guid isPermaLink="false">1407 at http://www.oehive.org</guid>
</item>
<item>
 <title>defaultframe</title>
 <link>http://www.oehive.org/prolint/rules/defaultframe</link>
 <description>&lt;h1&gt;&lt;strong&gt;undefined frame&lt;/strong&gt;&lt;/h1&gt;
&lt;p&gt;The rule &quot;defaultframe&quot; gives this message when it finds instances of DISPLAY and UPDATE statements that are not using a previously defined frame. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why use this rule?&lt;/strong&gt;&lt;br /&gt;
This can be useful when you are trying to identify user interface components in your code base. It can also be helpful for applying standards. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Solution&lt;/strong&gt;&lt;br /&gt;
Frames should be defined with either a DEFINE FRAME or FORMAT ... WITH statement.&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/prolint&quot; class=&quot;og_links&quot;&gt;Prolint&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://www.oehive.org/prolint/rules/defaultframe&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.oehive.org/prolint/rules/defaultframe#comments</comments>
 <category domain="http://www.oehive.org/taxonomy/term/462">contributed rules</category>
 <group domain="http://www.oehive.org/prolint">Prolint</group>
 <pubDate>Fri, 11 Jul 2008 13:09:04 +0000</pubDate>
 <dc:creator>blulow</dc:creator>
 <guid isPermaLink="false">1228 at http://www.oehive.org</guid>
</item>
<item>
 <title>nopprsininclude</title>
 <link>http://www.oehive.org/prolint/rules/nopprsininclude</link>
 <description>&lt;h1&gt;No Preprocessors in include&lt;/h1&gt;
&lt;p&gt;(explanation what this rule does, should go here. I don&#039;t know what the rule does)&lt;/p&gt;
&lt;p&gt;This is a contributed rule, which means it is not part of the standard Prolint setup but you can download it separately from the Subversion reporistory and save it in your local prolint/contribs/rules path.&lt;br /&gt;
See &lt;a href=&quot;http://www.oehive.org/node/1150&quot; title=&quot;http://www.oehive.org/node/1150&quot;&gt;http://www.oehive.org/node/1150&lt;/a&gt; for more information on contributed rules. &lt;/p&gt;
&lt;p&gt;Actually this is just an experiment, belonging to the proposal which is described in &lt;a href=&quot;http://www.oehive.org/node/1150&quot; title=&quot;http://www.oehive.org/node/1150&quot;&gt;http://www.oehive.org/node/1150&lt;/a&gt;&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/prolint&quot; class=&quot;og_links&quot;&gt;Prolint&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description>
 <comments>http://www.oehive.org/prolint/rules/nopprsininclude#comments</comments>
 <category domain="http://www.oehive.org/taxonomy/term/462">contributed rules</category>
 <group domain="http://www.oehive.org/prolint">Prolint</group>
 <pubDate>Sun, 04 May 2008 16:28:01 +0000</pubDate>
 <dc:creator>jurjen</dc:creator>
 <guid isPermaLink="false">1151 at http://www.oehive.org</guid>
</item>
<item>
 <title>Contributed rules</title>
 <link>http://www.oehive.org/node/1150</link>
 <description>&lt;p&gt;&lt;strong&gt;Traditional situation:&lt;/strong&gt;&lt;br /&gt;
Up until Prolint release 73, Prolint supports two groups of rules: standard rules and custom rules. Standard rules are installed as part of the Prolint distribution. Custom rules don&#039;t come from the Prolint website; a custom rule is created by the Prolint user and never committed to the Prolint website and hence not available to other users.&lt;br /&gt;
When someone wants to share their custom rules, they have to be accepted by project admin (=Jurjen) and then wait until the next Prolint release.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;New: Contributed rules&lt;/strong&gt;&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/prolint&quot; class=&quot;og_links&quot;&gt;Prolint&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://www.oehive.org/node/1150&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.oehive.org/node/1150#comments</comments>
 <category domain="http://www.oehive.org/taxonomy/term/462">contributed rules</category>
 <group domain="http://www.oehive.org/prolint">Prolint</group>
 <pubDate>Sun, 04 May 2008 13:08:17 +0000</pubDate>
 <dc:creator>jurjen</dc:creator>
 <guid isPermaLink="false">1150 at http://www.oehive.org</guid>
</item>
</channel>
</rss>
