From: Christian Neukirchen Date: 2006-06-17T01:28:12+09:00 Subject: Re: Why the lack of mixing-in support for Class methods? "Austin Ziegler" writes: > On 6/15/06, Yukihiro Matsumoto wrote: >> |Thankfully all the important ones (except #dup >> |and #clone) start with either '__' or 'instance_' (eg. __send__). But >> |#funcall will add another exception. It would be nicer to see a >> |consistant pattern in the naming of these meta-methods. >> Good point. We will have __funcall__ as well. Thank you. > > Should we have __dup__ and __clone__ and __class__ and __object_id__? Instead of further pythonizing the language (sorry, couldn't resist), I'd rather prefer a non-OO way for the tricky cases: Object.object_id_of myobj Object.class_of myobj Object.send_to myobj, :foo Maybe it's not optimal to make them singleton methods of Object, a module would probably be better. > -austin -- Christian Neukirchen http://chneukirchen.org