Advice for refactoring
From: Petterson Mikael (mikael.petterson_at_era.ericsson.se)
Date: 06/28/04
- Next message: Roedy Green: "Re: Advice for refactoring"
- Previous message: wayne.rawls: "Java in AT&T PWP"
- Next in thread: Roedy Green: "Re: Advice for refactoring"
- Reply: Roedy Green: "Re: Advice for refactoring"
- Reply: Lāʻie Techie: "Re: Advice for refactoring"
- Reply: Chris Smith: "Re: Advice for refactoring"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 28 Jun 2004 15:48:24 +0200
Hi,
I have two classes CardA and CardB that have a lot in common but with
some differences. Since a lot of code is duplicated my task is to remove
and find a solution to handle this.
CardA has implements two interfaces that CardB does not have. CardB
implements one interface that CardB does not have.
I am open to any suggestions, like rule of thumbs, on how to handle this
problem ( naming of classes, patterns....).
BR
//Mikael Petterson
- Next message: Roedy Green: "Re: Advice for refactoring"
- Previous message: wayne.rawls: "Java in AT&T PWP"
- Next in thread: Roedy Green: "Re: Advice for refactoring"
- Reply: Roedy Green: "Re: Advice for refactoring"
- Reply: Lāʻie Techie: "Re: Advice for refactoring"
- Reply: Chris Smith: "Re: Advice for refactoring"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|