From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <73eb3bfac904eb3dbc1f95bddfac1b46@rei2.9hal>
Date: Mon, 19 Nov 2012 14:22:33 +0100
From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
In-Reply-To: <nhjpn9x171.ln2@news.homelinux.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] c++
Topicbox-Message-UUID: d96bae90-ead7-11e9-9d60-3106f5b1d025

this is the problem. c++ programs follow a different
definition of "clean code" than idiomatic c programs.

by clean, they dont mean elegant or simple...

it usualy boils down to lots and lots of structure,
delegation and micro management and obsession with
consistency and patterns. there will be proxy classes
and visitor and mvc patterns and all that stuff and
a c++ programmer will call it clean code because it
follows constentent camel case naming and the funky
patterms can be looked up in some book, tho its
very hard to read or understand what the whole thing
is even supposed todo with all that indirection and
boiler plate.

--
cinap

PS: i think this is relevant:

Sometimes, the elegant implementation is just a function.
Not a method. Not a class. Not a framework. Just a function.
-- John Carmack