Timeline for Constructor-only subclasses: Is this an anti-pattern?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Mar 24, 2015 at 8:49 | audit | First posts | |||
| Mar 25, 2015 at 0:05 | |||||
| Mar 4, 2015 at 1:24 | comment | added | Phil | Point 1 is right on target. I didn't really understand point 2, but I'm sure it's just as good... :) | |
| Feb 27, 2015 at 20:27 | comment | added | HardlyKnowEm | Yeah, I think if I had to phrase the question over again, I'd say "code smell." It's not bad enough to warrant warning the next generation of young developers to avoid it, but it's something that if you see it, it may indicate that there is issue in the overarching design, but may also ultimately be correct. | |
| Feb 26, 2015 at 19:44 | history | answered | durron597 | CC BY-SA 3.0 |