From: Robert Klemme <shortcutter@...>
Date: 2010-05-27T22:09:56+09:00
Subject: Re: Badly organized code?

2010/5/27 Martin Hansen <mail@maasha.dk>:

> It is quite important to me that other people can put together a
> "Biopiece" as easily as possible i.e. expand the minimal example.
> Therefore I have moved code which under normal circumstances would be
> placed in the 'Biopieces' script to the Biopieces class - and I quite
> possibly violate a number of conventions that way.
>
>> I would extract the opion parsing from that class and either use a
>> Hash, OpenStruct or custom class for transportation of your options.
>> That way you make your bio pieces processing independent from the
>> interface (command line, graphical application etc.).
>
> I really don't want upcoming 'Biopiece writers' to fiddle around with
> other classes than the Biopieces class for the sake of simplicity - and
> I am willing to have option parsing and record parsing mixed even though
> it is ugly.

Well, then I don't know what you're after.  You say you suspect it's
badly structured, someone points out something that indicates bad
structure and you say you want to keep it that way.  What is your goal
and what do you expect from us?

Cheers

robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/