[#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:01214] Re: c-call and call in trace_func

From: matz@... (Yukihiro Matsumoto)
Date: 2000-02-01 03:32:36 UTC
List: ruby-talk #1214
Hi,

In message "[ruby-talk:01213] c-call and call in trace_func"
    on 00/01/31, Dave Thomas <Dave@thomases.com> writes:

|I'm trying to understand the difference between c-call and call events 
|in a trace function. Does anyone have any enlightenment?

`c-call' for C defined method calls, `call' for for Ruby defined
method calls.  The debugger cannot step into C defined methods, so
that the difference was caused.

							matz.

In This Thread

Prev Next