From: Brian Broom <ruby@...>
Date: 2007-05-01T23:29:56+09:00
Subject: Re: sprintf can not work in ruby c source?

------=_Part_159527_17125653.1178029794988
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 5/1/07, Peter Seebach <seebs@seebs.net> wrote:
>
> In message <f025162e5afe1e9c3304d79581fc4f24@ruby-forum.com>, Haoqi Haoqi
> writes:
> >I am not an experienced C programmer,and just learn to write a Ruby
> >extension with c.
>
> Don't.
>
> I consider myself a reasonably experienced C programmer, and I'd still
> want to be sure I was brushed up and current before trying to write an
> extension plugin.  Even in a well-planned environment, writing plugins
> is on the heavy-duty end.
>
> Seriously, just don't.  Hire someone.  Write it in pure Ruby.
>
> Or... Budget 3-6 months to learn C well enough to do it competently.
>
> -s
>
>
>
I'll disagree somewhat here.  There are things C does much faster than Ruby
does.  Application performance is not everything, but there are cases where
moving code to a C extension makes the difference between being able to use
ruby and not being able to.

Writing an extension in C is, to me, much easier than learning C by itself,
because there are a bunch of things that you can let ruby handle that are
just a pain in C (mainly I/O things).

------=_Part_159527_17125653.1178029794988--