in reply to your definition of KISS

From your description of the problem I get is that you have a bunch of variables, and you want to access them. You're also want a KISS solution, and then both you and your coworker discuss OO solutions.

The KISS is to use a struct. Or in Perl parlor, a hash.

Now, there may be all kinds of good reasons to use objects, but you want a KISS solution, you'd use a hash. There will be no DRY, with a hash you have 0 setters and getters.

Replies are listed 'Best First'.
Re^2: your definition of KISS
by klekker (Pilgrim) on Feb 08, 2012 at 09:31 UTC
    Well, somehow we got stuck keeping the existing OO approach since it was already there; sometimes it's hard to get a view from the outside by yourself...:/

    My greenfield approach would have been something like 
    if ($config->hasFeatureA()) {
// show feature A or put it into the container
}

    [download]
    (Depending on the project and just to get the idea).

    Thank you for your answer and sharing your point of view,
    k
[reply]
[d/l]

In Section Seekers of Perl Wisdom