From: ko1@...
Date: 2014-12-24T03:04:43+00:00
Subject: [ruby-core:67089] [ruby-trunk - Bug #10621] no parent in	rb_data_type_t

Issue #10621 has been updated by Koichi Sasada.


I'm okay to revert for avoiding parent.

However, I'm negative because parent abstraction is not good idea for rb_data_type_t.

Reasons:
* You can make such checking code in few lines with `data` field.
* mark, free, memsize doesn't care about `parent` (and difficult to care about `parent`. it depends on situations)
* `rb_data_type_t` is not an official API (so that README.ext doesn't refer on it)


----------------------------------------
Bug #10621: no parent in rb_data_type_t
https://bugs.ruby-lang.org/issues/10621#change-50602

* Author: Hans Mackowiak
* Status: Open
* Priority: Immediate
* Assignee: Nobuyoshi Nakada
* Category: core
* Target version: current: 2.2.0
* ruby -v: ruby 2.2.0dev (2014-12-19 trunk 48891) [x86_64-linux]
* Backport: 2.0.0: DONTNEED, 2.1: DONTNEED
----------------------------------------
`rb_data_type_t` does need to have a parent type otherwise it cant bind objects anymore that have a tree style ClassTree like in C++ or simulated with gtk

in C++ like Class B and Class C does inherit both Class A, cant be ported with ruby anymore because with that Class A cant have its own datatype anymore because the datatype check does break the inheritence. (id did worked before because it did had parent



-- 
https://bugs.ruby-lang.org/