Graeme Geldenhuys wrote:
Matt Emson het geskryf:
In my experience, often badly implemented and regularly abused.
Then whoever wrote that code you looked at has no clue what they were doing
and has a near zero understanding of design patterns or OOP.
No. The problem with Patterns is that you need to embrace or reject.
There's no middle ground.
Patterns take extreme discipline.
On the contrary, design patterns are everywhere,
Ah, yes. The old retro-fit argument. Name it and it shall be "so". You
guys crack me up ;-)
Patterns take extreme discipline because unless you adhere to them, your
code gets incredibly convoluted. Been there, seen it. Seen people use
them religiously, find a situation where performance tanked and use
unholy hacks to get around the issues. Again - they are fine, so long as
the development team wholeheartedly embraces them. Otherwise they are an
incredibly fine way to shoot yourself in the foot.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
