Wolfgang Jährling <[EMAIL PROTECTED]> writes:
> I think you're right. Instead of programming around Rubys failures,
> Ruby should be fixed. Unless it is fixed, we will limit ourself to
> single threaded translators. Since it really is an important issue
> for Ruby in general, it certainly will be
Yoshinori K. Okuji <[EMAIL PROTECTED]> wrote:
> 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. ;)
Well, not actually a guru, but an enthusias
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, t
asier!) c) Now we can claim that it's possible to
write translators in Ruby. :) I did _not_ assume that this is the way it
should be done and I have no problem with throwing away the code if the
Hurd hackers think that this approach is wrong.
- The second way would be to extend MiG (or
