Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!talisker.lacave.net!lacave.net!not-for-mail From: Kevin Mahler Newsgroups: comp.lang.ruby Subject: Re: What do you do when you need to attach data to an object instance? Date: Sat, 16 Apr 2011 12:53:31 -0500 Organization: Service de news de lacave.net Lines: 24 Message-ID: <1d1ebc367f9cde56225d927c8cbf0b4b@ruby-forum.com> References: <6fce5b6386258c51794d0b55b63e1ed6@ruby-forum.com> <41c1bcee810455547ca7d7844c1113d2@ruby-forum.com> <7b5e8d93ddba3dc3daa51fd319e3d800@ruby-forum.com> NNTP-Posting-Host: bristol.highgroove.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: talisker.lacave.net 1302976430 84016 65.111.164.187 (16 Apr 2011 17:53:50 GMT) X-Complaints-To: abuse@lacave.net NNTP-Posting-Date: Sat, 16 Apr 2011 17:53:50 +0000 (UTC) In-Reply-To: <7b5e8d93ddba3dc3daa51fd319e3d800@ruby-forum.com> X-Received-From: This message has been automatically forwarded from the ruby-talk mailing list by a gateway at comp.lang.ruby. If it is SPAM, it did not originate at comp.lang.ruby. Please report the original sender, and not us. Thanks! For more details about this gateway, please visit: http://blog.grayproductions.net/categories/the_gateway X-Mail-Count: 381708 X-Ml-Name: ruby-talk X-Rubymirror: Yes X-Ruby-Talk: <1d1ebc367f9cde56225d927c8cbf0b4b@ruby-forum.com> Xref: x330-a1.tempe.blueboxinc.net comp.lang.ruby:3016 7stud >> Because module_eval and class_eval are aliases, class_eval can be >> called on a module, a situation which is at worst wrong > >It certainly isn't "wrong"--ruby allows it. Wrong is not synonymous with illegal. One could easily argue that the alias is a mistake. class_eval, as the name suggests, should have been a more restricted version of module_eval. Allowing class_eval to have a module receiver is wrong because a module is not a class. I presented this as the "at worst" case--one end of the spectrum. >> and at best >> confusing. module_eval can never be wrong or confusing. Not a hard >> choice. > >I thought using module_eval was confusing in your code, and that was why >I suggested class_eval(). A class is a module. -- Posted via http://www.ruby-forum.com/.