Hi Murizio,
it is indeed hard sometimes manage some classes, but take also in
consideration that some of them - like the OgnlParser - are generated
by JavaCC and should not versioned in the SCM at all, there's an open
issue about it (OGNL-)
My suggestion would be: let's make first the current OGNL
On 18 May 2011 00:17, Stephen Williams wrote:
> The opposite, ravioli classes or when it goes very badly: "class diarrhea"
> (my term, see below), can be worse. When breaking down a business
> application, giant objects are usually a problem and something to avoid.
> When A) solving a complex an
The opposite, ravioli classes or when it goes very badly: "class diarrhea" (my term, see below), can be worse. When breaking down a
business application, giant objects are usually a problem and something to avoid. When A) solving a complex and tightly integrated
problem that should be used as s
if there is something I hate in programming is the god class [1].
OGNL seems to embrace god object's cause pretty well.
--
find -size +30k -name "*.java"| xargs -i sh -c "wc -l {}" |
