Refactoring squeak
stéphane ducasse
ducasse at iam.unibe.ch
Sat Jul 1 10:26:47 UTC 2006
If you want to increase the chance that your fixes get attention here
are some tricks.
- write tests to show that you do not break the system
- do not refactor for the sake of it
- use deprecation to support users of the old code
- ask people for feedback and review
- and yes having a better system is important (even if this is
difficult and may break some existing code)
Stef
On 30 juin 06, at 10:34, Damien Cassou wrote:
> Hi,
>
> sometimes when I dive into Squeak source code, I would like to
> refactor some piece of code that can be enhanced. Does someone care
> to have better source code in Squeak ? Where is the best place to
> post the enhancements ? To post new tests ? Often, it will be just
> one line or two, do I need to write bug reports in mantis ? Will
> somebody have a look at this ?
>
>
> Bye
>
More information about the Squeak-dev
mailing list
|