From: Robert Klemme <bob.news@...>
Date: 2005-06-01T17:40:22+09:00
Subject: Re: Operation on Classes

aartist wrote:
> The main idea is  about  creating templates.  In life and in general,
> when you encounter, existing set of conditions, you are most likely to
> do a solution that you already know for those conditions.  Consider
> conditions as set of items and you should know the operations that you
> can perform with given set of items.
>
> Here, my attept is to document all templates, possible for the basic
> classes that Ruby Provides. I can convert the given problem into set
> of known items,  and then I can apply template that can match.  So  it
> become very easy to know what is possible. This can reduce lots of
> mental efforts, while programming..

If I understand you correctly you kind of want to introduce static typing
through the backdoor.  There has been a lot of debate about this, whether
static typing should be present in Ruby and how it can be done.  You'll
find it in the archives:
http://blade.nagaokaut.ac.jp/ruby/ruby-talk/index.shtml

Apart from the static typing issue: this sounds like a brute force
approach to development that I still fail to see the benefits of.  At
least it seems to me the effort is much too high vs. the benefits gained -
if it works at all.  Do you know any success stories where this approach
has been applied?

Also, determining input and output types doesn't tell you the semantics of
a method.  You need more detailed information about the properties of the
pre and after states.

Kind regards

    robert