On Sat, 18 Nov 2006 16:26:58 -0800, Paul Lutus wrote:

> n/a wrote:
> 
>> On Sat, 18 Nov 2006 16:00:07 -0800, Paul Lutus wrote:
>> 
>>> In such cases, I sometimes prototype in Ruby, because development is so
>>> fast, and then translate the result from Ruby into C++ once I have a
>>> working program, so the delivered program will be fast.
>> 
>> tx a lot 4 the feedback, Paul.  i will take e/g into consideration.
>> 
>> let me ask u how the the translation from ruby to c++ is done....
> 
> By a human. e.g. me. It's not automated. It might be sometime in the future,
> but remember that hand-written C++ is always faster, when done by someone
> with some depth of knowledge.
> 
>> 
>> (that wd make the case even more to go ahead and start w/ ruby and
>> translate to c++ in some cases where it wd be needed; & stick w/ ruby the
>> rest of the time....)
> 
> You shouldn't expect an automated Ruby to C++, or for that matter a Java to
> C++, automatic translator, in the foreseeable future.
>

ok, tx 4 clearing that up.  it means that u must have knowledge of both
languages, obviously....and the point re. starting w/ a more intuitive
language such as ruby is of interest