helmut.rohregger at gmail.com
Sat Apr 26 14:40:02 UTC 2014
To clarify things: I am writing a squeak byte code interpreter in Java,
which is still in experimental stage. To test my interpreter, I have
written test cases in squeak, which get executed in my interpreter...
Am 24.04.2014 11:54, schrieb Frank Shearar:
> That confuses me, because people usually implement their tests as
> instance methods of a TestCase subclass.
> I wouldn't be surprised if writing your test cases as class-side
> methods didn't break something in tooling that might well expect to
> see instance methods.
> On 23 April 2014 20:09, Helmut Rohregger <helmut.rohregger at gmail.com> wrote:
>> Hi Andreas,
>> thanks for your response.
>> This is just a test class, where every single method is a test case. I
>> implemented this class when I started to learn Squeak and implemented
>> this test cases by mistake at the instance side of the test class...
>> - Helmut
>> Am 23.04.2014 18:51, schrieb Andreas Wacknitz:
>>> Hi Helmut,
>>> Am 23.04.2014 um 08:18 schrieb Helmut Rohregger <helmut.rohregger at gmail.com>:
>>>> because I didn't get response to my question in the beginners list, I
>>>> post it here.
>>>> Is there an easy way to change instance methods to class methods?
>>>> I know it is possible to drag and drop single methods. But I am looking
>>>> for the possibility to move 100+ methods at once.
>>>> - Helmut
>>> Are you really trying to move 100+ methods within a single class?
>>> If so that sounds utterly wrong. And moving from the instance side to the class side is even worse.
>>> This smells like putting a single class around your old non-OO code.
>>> If you don’t have REALLY good reasons to have such a number of methods in a class you should
>>> consider to refactor the class into several classes.
>>> This wouldn’t prevent you from having the problem to move methods around but would lessen the pain.
More information about the Squeak-dev