https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112011-07-24T14:31:21ZRuby Issue Tracking SystemRuby master - Feature #5088: Refactor and Document vm_method.c / method.hhttps://bugs.ruby-lang.org/issues/5088?journal_id=196092011-07-24T14:31:21Zgnufied (hemant kumar)gethemant@gmail.com
<ul></ul><p>@Ilias,</p>
<p>Please submit any improvement with a patch. It is pointless to open a request without a patch and with due respect - wastes Ruby-Core valuable time.</p> Ruby master - Feature #5088: Refactor and Document vm_method.c / method.hhttps://bugs.ruby-lang.org/issues/5088?journal_id=196102011-07-24T16:16:47Zlazaridis.com (Lazaridis Ilias)ilias@lazaridis.com
<ul></ul><p>=begin<br>
hemant kumar wrote:</p>
<blockquote>
<p>@Ilias,</p>
<p>Please submit any improvement with a patch. It is pointless to open a request without a patch</p>
</blockquote>
<p>Mr. Kumar, I don't know who you are, but the rule you state is not existent within this project.</p>
<blockquote>
<p>and with due respect - wastes Ruby-Core valuable time.</p>
</blockquote>
<p>I guess it distracts the list from the relevant stuff, like making jokes: <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Compress a sequence of ends (Rejected)" href="https://bugs.ruby-lang.org/issues/5054">#5054</a> ?</p>
<ul>
<li>
</ul>
<p>As I've possibly not expressed myself clear:</p>
<ul>
<li>Task announced, asking for general objections.</li>
<li>If no objections, I'll continue and provide the patches (which can of course be objected/rejected)</li>
</ul>
<p>=end</p> Ruby master - Feature #5088: Refactor and Document vm_method.c / method.hhttps://bugs.ruby-lang.org/issues/5088?journal_id=196682011-07-25T21:48:49Zlazaridis.com (Lazaridis Ilias)ilias@lazaridis.com
<ul></ul><p>=begin</p>
<p>You can follow the rework on this location:</p>
<p>((<a href="URL:https://github.com/lazaridis-com/ruby/tree/refactor_vm_method" class="external">URL:https://github.com/lazaridis-com/ruby/tree/refactor_vm_method</a>))</p>
<p>What is the preferred method? Sending refactoring patches one-by-one for commit, or as a one big patch when it's finished?</p>
<p>=end</p> Ruby master - Feature #5088: Refactor and Document vm_method.c / method.hhttps://bugs.ruby-lang.org/issues/5088?journal_id=251582012-03-25T17:21:55Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Assigned</i></li><li><strong>Assignee</strong> set to <i>ko1 (Koichi Sasada)</i></li></ul> Ruby master - Feature #5088: Refactor and Document vm_method.c / method.hhttps://bugs.ruby-lang.org/issues/5088?journal_id=274412012-06-26T05:29:08Zko1 (Koichi Sasada)
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Closed</i></li></ul><p>I think we need to discuss about each spec, before implementation (of course, a proposal with an implementation is welcome). Please persuade matz before you try to commit your patch.</p>