<?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 - transaction scope</title>
 <link>http://www.oehive.org/taxonomy/term/352/0</link>
 <description></description>
 <language>oehive</language>
<item>
 <title>new rule help</title>
 <link>http://www.oehive.org/node/870</link>
 <description>&lt;p&gt;Hi, all.&lt;/p&gt;
&lt;p&gt;We just recently acquired proparse and prolint.  I am looking into writing some new rules.  I have not finished reading all the doc available at joanju.com, or fully absorbed the syntax tree.  But I was hoping you folks could help me short-circuit the process a little.  I am wondering if any of you&lt;br /&gt;
a) have written these rules&lt;br /&gt;
b) have suggested starting points to help me locate how to find them in the tree&lt;br /&gt;
c) be able to tell me &quot;No can do&quot;&lt;/p&gt;
&lt;p&gt;on several rules I am looking at implementing.&lt;br /&gt;
1) No nested includes&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/870&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.oehive.org/node/870#comments</comments>
 <category domain="http://www.oehive.org/taxonomy/term/105">Prolint</category>
 <category domain="http://www.oehive.org/taxonomy/term/351">include files</category>
 <category domain="http://www.oehive.org/taxonomy/term/350">new rules</category>
 <category domain="http://www.oehive.org/taxonomy/term/352">transaction scope</category>
 <group domain="http://www.oehive.org/prolint">Prolint</group>
 <pubDate>Tue, 29 May 2007 18:23:01 +0000</pubDate>
 <dc:creator>gwest</dc:creator>
 <guid isPermaLink="false">870 at http://www.oehive.org</guid>
</item>
</channel>
</rss>
