http://www.oehive.org/taxonomy/term/192/0 oehive http://www.oehive.org/node/1524 <p>If hard coded email is found in an include file, this rule shows the original procedure as source.<br /> E.g. if I have procedure proc.p which is</p> <p>/* proc.p body */<br /> /* ... some code */<br /> {inc.i}<br /> /* ... some code */</p> <p>hard coded email is in inc.i</p> <p>Though proLint will show me that source is proc.p, not inc.i. The line will be the correct line in inc.i</p> <p>Attached is a changed rule, which seems to work fine.</p> <p>Yuri</p> <br class="clear" /><div class="og_rss_groups"><ul class="links"><li class="first last og_links"><a href="/prolint" class="og_links">Prolint</a></li> </ul></div> http://www.oehive.org/node/1524#comments Prolint bug nohardcodeemail Prolint Fri, 25 Sep 2009 15:59:18 +0000 Yuri 1524 at http://www.oehive.org http://www.oehive.org/node/629 <p>As you probably know, Progress Software doesn't list most of the known bugs of the latest OpenEdge version.<br /> I sometimes waste a couple of hours (...days) on something, make a call to Progress tech support just to know from them that my problem is due to a bug they already know about.<br /> From my calls to tech support, I also get a new "official" bug number for new bugs that they didn't knew about (including documentation bugs ("doc bugs") i.e. something in the documentation that is wrong or too incomplete... this too causes to loose precious time sometimes).</p> <p>How about having a new Hive sectio</p> <br class="clear" /><p><a href="http://www.oehive.org/node/629">read more</a></p> http://www.oehive.org/node/629#comments Hive group bug official tech support technical support Mon, 16 Oct 2006 16:31:25 +0000 dlauzon 629 at http://www.oehive.org