From: Robert Klemme <shortcutter@...>
Date: 2009-08-01T21:40:05+09:00
Subject: Re: how to stop the subclass from overriding a method.

On 31.07.2009 13:59, Venkat Akkineni wrote:
>> It will certainly work but you'll end up with Java written
>> with Ruby syntax.
> 
> This was playing in the back of my head. But makes more sense when 
> detailed from another person's perspective.  A sensible argument one 
> would expect from purists.

I am not sure I qualify as purist.  I just tried to step back and think 
about what the consequences of your endeavor would be.

>           Hence I have given up trying perfect my java -> ruby 
> translation skills. The focus now is on how to implement the classes 
> better in ruby using the language features. The price is time which we 
> have agreed on paying. We could do the API from the scratch but feel 
> that would consume a lot of time in requirements analysis itself let 
> alone development and testing.

What you can do IMHO is look at the original Java design to find out 
which tasks have to be done and how the code is structured.  Chances are 
that you will find more important and well designed Java classes also in 
your Ruby version.  That way you at least have a mental framework which 
surely helps in redeveloping the application in Ruby.  So you are 
actually only throwing code away but not ideas - and these seem to be 
much more important.

Kind regards

	robert

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