<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 6: Change to local variable naming scheme</title><link>https://sourceforge.net/p/jode/feature-requests/6/</link><description>Recent changes to 6: Change to local variable naming scheme</description><atom:link href="https://sourceforge.net/p/jode/feature-requests/6/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 16 Oct 2001 02:23:46 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/jode/feature-requests/6/feed.rss" rel="self" type="application/rss+xml"/><item><title>Change to local variable naming scheme</title><link>https://sourceforge.net/p/jode/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Instead of naming the local variables numerically &lt;br /&gt;
across all methods, it would be nice to have the &lt;br /&gt;
option to restart the numbering with each method.&lt;/p&gt;
&lt;p&gt;This speciifcally addresses the diffculty with which &lt;br /&gt;
one can quantify the changes between two &lt;br /&gt;
releases of a third party jar.&lt;/p&gt;
&lt;p&gt;I.e. if I decompile a particular jar's contents, then &lt;br /&gt;
use diff to diff the two versions of a particular class, &lt;br /&gt;
everything matches up perfectly except for if a &lt;br /&gt;
change included-- say-- adding a local variable to &lt;br /&gt;
a function.&lt;/p&gt;
&lt;p&gt;In that case, it causes all subsequent methods &lt;br /&gt;
with local variables of the same type to report lots &lt;br /&gt;
of changes because of the local variable &lt;br /&gt;
numbering scheme.&lt;/p&gt;
&lt;p&gt;If the local variable numbering system reset itself &lt;br /&gt;
at each method, this wouldn't happen.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bill Bumgarner</dc:creator><pubDate>Tue, 16 Oct 2001 02:23:46 -0000</pubDate><guid>https://sourceforge.net314ebd466c7bccbf18c2c95f7c2a88c20fd3e7fd</guid></item></channel></rss>