[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Translators in Ruby

From: Yoshinori K. Okuji
Subject: Re: Translators in Ruby
Date: Wed, 09 Jan 2002 02:05:17 +0900
User-agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (Unebigoryoae) APEL/10.3 Emacs/20.7 (i686-pc-linux-gnu) MULE/4.0 (HANANOEN)

At Tue, 8 Jan 2002 02:57:48 +0100,
Wolfgang Jährling wrote:
> I want to write translators in the Ruby programming language, so I thought
> about what would need to be done to achive this.

I'm very happen to see a Ruby guru here. ;)

> - Ruby is not threadsave. When using Ruby and POSIX threads, the Ruby
>   interpreter crashs badly.

IMHO, Ruby should be blamed here. Ruby needs not to be multithreaded,
but it should take it into account to be used with a multithreaded
environment. Probably as you know, that problem appears not only on
the Hurd (e.g. also with multithreaded applications such as Apache

> - The first one might be seen as a quick hack by some people, but it's the
>   way one usually extends Ruby. One would write a wrapper for libtrivfs, one
>   for libnetfs and so on.

Is it possible to use SWIG for Hurd libraries? As the libraries are
quite large, it would be easier to maintain wrappers with SWIG than to
write everything in C. This might enable to share code with Perl
extensions for Hurd.

> - The second way would be to extend MiG (or flick or something
> else).

I think it wouldn't be so hard to write a MiG-to-SWIG converter.


Are you enbugging Free Software?   <URL:>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]