Issue #5088 has been updated by Lazaridis Ilias.


=begin

You can follow the rework on this location:

((<URL:https://github.com/lazaridis-com/ruby/tree/refactor_vm_method>))

What is the preferred method? Sending refactoring patches one-by-one for commit, or as a one big patch when it's finished?

=end

----------------------------------------
Feature #5088: Refactor and Document vm_method.c / method.h
http://redmine.ruby-lang.org/issues/5088

Author: Lazaridis Ilias
Status: Open
Priority: Normal
Assignee: 
Category: core
Target version: 


=begin
(not a "Feature" but a "Task")

Refactoring and documentation of the following files:

* source:vm_method.c
* source:method.h
* other indirectly affected files

This will not alter the functionality in any way, but will change only whitespace, structure and naming.

The goals are 
* to make the method handling easier to understand.
* to enable more developers to maintain the code
* To simplify processing/implementation of issues: #4893, #5005
* To simplify the completition/extension of the method-handling
* to prepare for a later redesign of vm_method.c (towards "methods are objects")

(patches follow by time, if no objecting is given)

=end



-- 
http://redmine.ruby-lang.org