将所有语句从一种方法移动到另一种方法-Movingallstatementsfromonemethodtoanother

0  

The technique of moving code without altering the behavior of the code is called Refactoring and is nicely covered in a book by Martin Fowler.

在不改变代码行为的情况下移动代码的技术称为重构，并在Martin Fowler的书中很好地介绍。

In your case, I would take the following multi-step approach:

在您的情况下，我将采取以下多步骤方法：

1. Stand up a "do nothing" function in the function you wish to split, just above the lines of code you wish to move.
2. 在要分割的功能中站起来“无所事事”功能，就在您想要移动的代码行的上方。
3. Move one or two of those lines of code from the surrounding function int the "do nothing" function, splitting the function, but having the split be a nested call.
4. 将这些代码行中的一行或两行从周围的函数移动到“do nothing”函数中，拆分函数，但将split拆分为嵌套调用。
5. Move the split function up (or down) to the edge of the block in the surronding function.
6. 将分割功能向上（或向下）移动到surronding功能中的块边缘。
7. Move teh slpit function out of the block, placing new calls to it either prior to every call of the original function, or after every call of the original function. Note that you may have to rework the handling of return parameters, depending on the details.
8. 将slh slpit函数移出块，在每次调用原始函数之前或每次调用原始函数之后对其进行新调用。请注意，您可能需要重新处理返回参数，具体取决于详细信息。

It is strongly suggested that you write a set of tests to validate some, if not most, of the overall functionality of this block first. Then, after each change run your tests to verify that you didn't change behavior.

强烈建议您编写一组测试来首先验证此块的一些（如果不是大多数）整体功能。然后，在每次更改后运行您的测试以验证您没有更改行为。

What you are seeing now is a change in behavior which came about by modifying the text of the code in such a manner that it did change behavior. The set of safe transformations of source code is likely smaller than you previously believed, or maybe you just made a simple error. However, the work you are attempting requires more knowledge than can be expressed in a StackOverflow style, question / answer, format. That's why I made the book reference.

你现在看到的是行为的改变，这是通过修改代码文本以改变行为的方式而产生的。源代码的安全转换集可能比您之前认为的要小，或者您可能只是犯了一个简单的错误。但是，您正在尝试的工作需要的知识多于StackOverflow样式，问题/答案，格式。这就是我写这本书的原因。

If you can narrow the scope, you might get a better response in a future resubmission.

如果您可以缩小范围，则可能会在将来的重新提交中获得更好的响应。

0  

It seems that moving stmts just doesn't work. In contrast, completely replacing the body

移动stmts似乎不起作用。相比之下，完全取代了身体

        Body originalBody = sm.getActiveBody();
        originalBody.setMethod(auxMethod);
        auxMethod.setActiveBody(originalBody);
        Body newBody = Jimple.v().newBody(sm);
        sm.setActiveBody(newBody);

and then regenerating the locals, identity stmts (and other stmts you may need) in the newBody looks like a sensible way to go.

然后在newBody中重新生成本地人，身份stmts（以及你可能需要的其他stmts）看起来是一种明智的方式。