On Sunday, 17 June 2018 at 12:24:35 UTC, FromAnotherPlanet wrote:
What's the differences in the approaches between SOLID and
component programming? Are they orthogonal? Or can they be used
together?
It looks like they have some overlap, but are not the same. SOLID
seems focused on OOP, wherea
What's the differences in the approaches between SOLID and
component programming? Are they orthogonal? Or can they be used
together?
On Saturday, 16 June 2018 at 19:20:30 UTC, FromAnotherPlanet
wrote:
- Interface segregation principal: Essentially breaking the
program up into smaller interfaces. Sometimes only consistent
of one or two methods/properties (can feed into 'S' of SOLID
quite nicely).
- Dependency inversion pr
On Sunday, 17 June 2018 at 01:38:17 UTC, evilrat wrote:
On Saturday, 16 June 2018 at 19:20:30 UTC, FromAnotherPlanet
wrote:
Hi, I come from a C# background and have been looking at D.
How well does D implement solid principals? I've grown to
really enjoy the SOLID style.
For those unfamiliar,
On Saturday, 16 June 2018 at 19:20:30 UTC, FromAnotherPlanet
wrote:
Hi, I come from a C# background and have been looking at D. How
well does D implement solid principals? I've grown to really
enjoy the SOLID style.
For those unfamiliar, SOLID is an acronym for:
- Single purpose: Meaning eve
Hi, I come from a C# background and have been looking at D. How
well does D implement solid principals? I've grown to really
enjoy the SOLID style.
For those unfamiliar, SOLID is an acronym for:
- Single purpose: Meaning every unit of code (whether it's a
function or class) should only
have
On Saturday, 16 June 2018 at 19:20:30 UTC, FromAnotherPlanet
wrote:
Hi, I come from a C# background and have been looking at D. How
well does D implement solid principals? I've grown to really
enjoy the SOLID style.
For those unfamiliar, SOLID is an acronym for:
- Single purpose: Meaning eve
