From: Seebs Date: 2010-05-08T04:55:09+09:00 Subject: Re: ease of porting (translating) ruby to C (vs. python)? On 2010-05-07, bwv549 wrote: > In a very small bioinformatics group I know of, they are deciding > whether to code mostly in python or ruby. The lead knows that python > can "easily be ported to C because of its strictness." Let me be as polite as possible: That's a bunch of bullshit. I would find it reasonably difficult to port code from ANY scripting language to C -- and I'm pretty good at C. "Strictness" does not make it easier to port python to C. Nor does it make it easy to port shell to C, or perl to C, or anything else. I am afraid the lead is full of crap. Sometimes this happens. Furthermore, porting stuff from an OO language to C is almost certainly absolutely the wrong thing to do. The correct solution might be to write a plugin module for the language which translates specific functionality into raw C calls for performance reasons, but if you have a design that makes any sense at all in an OO language, translating it to C is stupid. In any event, what you have here is a social problem, not a technical problem -- you have someone in charge who doesn't know what's going on. -s -- Copyright 2010, all wrongs reversed. Peter Seebach / usenet-nospam@seebs.net http://www.seebs.net/log/ <-- lawsuits, religion, and funny pictures http://en.wikipedia.org/wiki/Fair_Game_(Scientology) <-- get educated!