[#955] Ruby 1.4.3 — Yukihiro Matsumoto <matz@...>
Ruby 1.4.3 is out, check out:
1 message
1999/12/07
[#961] Ruby compileable by C++ compiler? — Clemens Hintze <c.hintze@...>
Hi,
8 messages
1999/12/10
[#962] Re: Ruby compileable by C++ compiler?
— matz@... (Yukihiro Matsumoto)
1999/12/10
Hi,
[#963] Re: Ruby compileable by C++ compiler?
— Clemens Hintze <clemens.hintze@...>
1999/12/10
Wei,
[#964] Bastion or SecurityManager for Ruby? — Clemens Hintze <clemens.hintze@...>
Hi,
15 messages
1999/12/10
[#966] Re: Bastion or SecurityManager for Ruby?
— nakajima kengo<ringo@...>
1999/12/10
Hello Clemens,
[#967] Re: Bastion or SecurityManager for Ruby?
— matz@... (Yukihiro Matsumoto)
1999/12/10
Hi,
[#989] a question about to_i — Friedrich Dominicus <Friedrich.Dominicus@...>
Sorry, I'm quite new to ruby. But I encounterd the following problem. If
17 messages
1999/12/19
[ruby-talk:00961] Ruby compileable by C++ compiler?
From:
Clemens Hintze <c.hintze@...>
Date:
1999-12-10 07:59:28 UTC
List:
ruby-talk #961
Hi, perhaps, I want to try to embed the ruby interreter in an application of mine. But unfortunately, this application would be compiled with a C++ compiler! In fact, on the target platform, there is no C compiler at all! That means, I have to compile ruby also with a C++ compiler. But many functions in the sources of ruby are declared/defined in K&R C-manner. That will not be accepted by our C++ compiler. However, if I decide that I would like to embed ruby, I probably could modify the sources so that they become compileable by an C++ compiler. My question would be now: Is there any interest in this? If the community means, they wouldn't like this idea, I would not even try this. Because I would have to do it on all new releases again. But if this idea would be accepted, I *probably* would do it, *if* I decide that I really go this way. I would pass the necessary modifications to ruby-talk, so that they would find its way into the official releases. So what it your meaning about this ... ? Let us discuss it! :-))) Ciao, \cle -- Clemens Hintze mailto: c.hintze@gmx.net