[#1263] Draft of the updated Ruby FAQ — Dave Thomas <Dave@...>

33 messages 2000/02/08

[#1376] Re: Scripting versus programming — Andrew Hunt <andy@...>

Conrad writes:

13 messages 2000/02/15

[#1508] Ruby/GTK and the mainloop — Ian Main <imain@...>

17 messages 2000/02/19
[#1544] Re: Ruby/GTK and the mainloop — Yasushi Shoji <yashi@...> 2000/02/23

Hello Ian,

[#1550] Re: Ruby/GTK and the mainloop — Ian Main <imain@...> 2000/02/23

On Wed, Feb 23, 2000 at 02:56:10AM -0500, Yasushi Shoji wrote:

[#1516] Ruby: PLEASE use comp.lang.misc for all Ruby programming/technical questions/discussions!!!! — "Conrad Schneiker" <schneiker@...>

((FYI: This was sent to the Ruby mail list.))

10 messages 2000/02/19

[#1569] Re: Ruby: constructors, new and initialise — Yukihiro Matsumoto <matz@...>

The following message is a courtesy copy of an article

12 messages 2000/02/25

[ruby-talk:01294] [HELP]: Compile Error on DEC alpha.

From: Clemens Hintze <clemens.hintze@...>
Date: 2000-02-10 11:48:23 UTC
List: ruby-talk #1294
Hello matz,

I have tried to compile Ruby 1.4.3 on a "OSF1 slbhdg V4.0 1229 alpha"
with the native compiler (means *not* GCC).

There are many warnings. But with additional options "-w -std", I
could compile it at least. Until there were compile errors in file
parse.y!

The compiler moans, that the function 'call_op' is called with 3
arguments instead of 4. This happens in the lines: 715, 727, 789.

Could you explain me, please, how to correct these lines? 

I have tried to append a '0' (ZERO) as the last parameter. It
compiles, but during execution of 'miniruby extconf.rb' in the 'ext'
subdirectories, there is a GC caused SIGSEGV sometimes. I don't know,
whether this is related to my stupid fix attempt.

I have not taken the GCC on purpose, as on our integration machine,
there will be no GCC. Only the native one.

Waiting of enlightment ... 

\cle

In This Thread

Prev Next