[#237] object.c ruby.h (fwd) — Robert Skarwecki <skaav@...>

Hello everybody,

42 messages 2002/07/24
[#239] Re: [PATCH] object.c ruby.h (fwd) — GOTO Kentaro <gotoken@...> 2002/07/24

At Thu, 25 Jul 2002 00:02:28 +0900,

[#240] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/24

GOTO Kentaro <gotoken@notwork.org> writes:

[#246] Re: [PATCH] object.c ruby.h (fwd) — GOTO Kentaro <gotoken@...> 2002/07/25

At Thu, 25 Jul 2002 05:05:46 +0900,

[#247] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/25

GOTO Kentaro <gotoken@notwork.org> writes:

[#248] Re: [PATCH] object.c ruby.h (fwd) — nobu.nokada@... 2002/07/25

Hi,

[#249] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/25

nobu.nokada@softhome.net writes:

[#250] Re: [PATCH] object.c ruby.h (fwd) — nobu.nokada@... 2002/07/25

Hi,

[#252] Re: [PATCH] object.c ruby.h (fwd) — GOTO Kentaro <gotoken@...> 2002/07/25

At Fri, 26 Jul 2002 03:11:02 +0900,

[#253] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/25

GOTO Kentaro <gotoken@notwork.org> writes:

Re: A couple of questions on writing extensions

From: nobu.nokada@...
Date: 2002-07-26 00:56:48 UTC
List: ruby-core #257
Hi,

At Fri, 26 Jul 2002 06:09:35 +0900,
Matthew Bloch wrote:
> *) what does 'Died with exception wrong argument type Object (expected Data)' 
> mean?

Literally, you passed something else to the method expecting
Data.

> which is nothing to do with my converted class, but the error implies 'key' is 
> somehow corrupt or of the wrong type, where the same code worked before.  
> This exception seems to be thrown from different points depending on timing 
> (though more often than not in a simple call to a logger), which is pretty 
> difficult to track down.

I vote GC issue.  How do you define mark/free functions for
Data_{Make,Wrap}_Struct?  Could you show us the source?

> *) Is this kind of construct safe as the end of a bog-standard native accessor 
> method? :

Yes.

> i.e. constructing a temporary object with the same value as the one inquired 
> about?  Might it be garbage collected before being read by the Ruby caller?  
> Will it be garbage-collected when the result goes out of context in the 
> calling Ruby method?

While it is referred by `self', never collected.

> *) is this a correct way to call back a method implemented in class derived 
> from a C extension class? :

Yes.

In This Thread