From: ccos <ccos@...>
Date: 2003-03-01T15:41:16+09:00
Subject: how is ruby's timing?

hi,

i'm thinking of using ruby as a scripting
language for a multimedia system that i'm
writing in C++. not to go into too much detail,
the general idea is to have sound and image synthesis
very closely tied, sharing buffers and what not. it's still very very 
much
in the design stages.

i would like it to eventually be capable of real-time and non-real-time
operation. my question is about real time useage, because for
non real time stuff ruby would be perfect i'm sure.

for real time use i would need millisecond accurate timing,
and i'm concerned about unwanted dropouts and timing
variations imposed by memory management and
threading in the ruby interpreter.

i've also considered three implementation options and am leaning
strongly towards the last:

embedding the language interpreter
into the app.

extending the interpreter,
using ruby's bindings to C

having the ruby interpreter as a network client
to a media server written entirely in C++

just wondering if anybody could give any advice
on which route they would recommend, and also give some
general advice on ruby's gc and threading, all in the light
of my real-time requirements.

anybody done anything remotely similar in ruby?

thanks much,
c