Forum: Ruby Q: hash parameter passed to c++ ruby extension is incomplete

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Ddfc57eb5375d489a6387ea838eb7af5?d=identicon&s=25 Yuri Danielyan (yurid)
on 2009-03-11 09:20
I'm trying to pass following hash to my c++ ruby extension:
h1 = {"G804988.19" => 0, "G804988.21" => 0, "NH3812.06" => 0,
"NH3812.10" => 0}
myext.SomeFunction(h1)

The hash looks fine from script:
h1.each_pair {| key, value | printf("%s - %s\n",  key, value) }

The above statement shows that all 4 hash entries are there.


But in the extension I can only see 3 items.
Code is like below:

extern "C" VALUE SomeFunction(VALUE vSelf,VALUE vh1)
{
  struct st_table  *pTblHash;

  pTblHash = RHASH(vh1)->tbl;
}

The pTblHash->num_entries is correct and equals to 4.
But in the pTblHash->bins array there are only 3 not empty pointers to
hash elements.

If I use one symbol shorter hash keys for one of entries (G80498.21
instead of G804988.21), for example:
h1 = {"G804988.19" => 0, "G80498.21" => 0, "NH3812.06" => 0, "NH3812.10"
=> 0}

then problem disappears.

I'm debugging under Windows XP and Ruby 1.8.

I'll appreciate any help.
Thank you.
Yuri
666b4e17b4bb0e2d999037a25f65a7cb?d=identicon&s=25 Heesob Park (phasis)
on 2009-03-11 10:18
(Received via mailing list)
Hi,

2009/3/11 Yuri Danielyan <yurid@synopsys.com>:
>
> The pTblHash->num_entries is correct and equals to 4.
> I'm debugging under Windows XP and Ruby 1.8.
>
I guess the problem is due to the Collision resolution [1].

The st_table, num_entries and bins are highly implementation dependent
so using it directly in extension code is not recommended.

In my experience, almost all extension codes required hash could be
done with following rb_hash_xxx functions
rb_hash_new
rb_hash_delete
rb_hash_foreach
rb_hash_aref
rb_hash_aset


[1] http://en.wikipedia.org/wiki/Hash_table#Collision_resolution

Regards,

Park Heesob
Ddfc57eb5375d489a6387ea838eb7af5?d=identicon&s=25 Yuri Danielyan (yurid)
on 2009-03-11 10:42
Heesob Park wrote:
> I guess the problem is due to the Collision resolution [1].
>
> The st_table, num_entries and bins are highly implementation dependent
> so using it directly in extension code is not recommended.
>
> rb_hash_foreach

Thank you
Actually I started with using rb_hash_foreach, but sometimes I don't see
this function in intern.h (probably older Ruby versions), so I turned to
direct usage.
But after your reply I thought that maybe there are two items under same
bin and I can reach it somehow.
This topic is locked and can not be replied to.