From: Tilman Sauerbeck Date: 2006-02-15T06:48:37+09:00 Subject: undefining Class.inherited makes class not subclassable anymore --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, 1.) cFoo =3D rb_define_class ("Foo", rb_cObject); 2.) rb_define_singleton_method (cFoo, "inherited", ...) 3.) rb_undef_method (rb_singleton_class (foo, "inherited")) 4.) rb_define_class (c, "Bar", cFoo) The fourth call will lead to an error saying: "Undefined method 'inherited'" Is there a way to restore the default Class.inherited method on Foo, so I can still inherit from Foo, but not call the original inherited method I defined in step 2? Thanks, Tilman --=20 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? --liOOAslEiF7prFVr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD8lAj27uLisrW2w8RAtRxAJ9i4q60iN8yq2bZKJcKSMpQv+Nz1ACcDzuV 3jdn3vrQ0UucZne6IElq53A= =l+1v -----END PGP SIGNATURE----- --liOOAslEiF7prFVr--