[#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:00965] Re: Ruby compileable by C++ compiler?
From:
kjana@... (YANAGAWA Kazuhisa)
Date:
1999-12-10 11:13:43 UTC
List:
ruby-talk #965
In message <14416.49702.585411.416016@gargle.gargle.HOWL> clemens.hintze@alcatel.de writes: > Fortunately there is a GCC available ;-))) > > But for my project, it is requested to use a C++ compiler. It would be > a pitty if I couldn't use Ruby here, only because it sticks to old > syntax, wouldn't it? What about protoize or any other program which converts K&R style C sources to ANSI-C style? Or does that compiler has some option which enables K&R style source? # It may be the option supports C source, or implicit behavior change # according to suffixes of source files. By the way, You should take care of incompatibilities between C and C++. I don't know well, but it may confuse behavior of the program. # Well, I really have no idea what may happen. It is possible that no # problem happen and whole project go well :-) > But we should also hear opinions of other member. So please share our > discussion :-))) There are many good tools for converting source between K&R-ANSI, so a programmer's favorite should be important. Therefore I think the style of ruby's source should be style the author of ruby like. -- kjana@os.xaxon.ne.jp December 10, 1999 Abstract should not be abstract.