From: Ilias Lazaridis <ilias@...>
Date: 2005-04-04T20:44:44+09:00
Subject: Re: [EVALUATION] - E03 - jamLang Evaluation Case Applied to Ruby

Csaba Henk wrote:
> On 2005-04-04, Robert Klemme <bob.news@gmx.net> wrote:
> 
>>"Saynatkari" <ruby-ml@magical-cat.org> schrieb im Newsbeitrag 
>>
>>>You are not accessing the method, you are _calling_ the method.
>>>As mentioned earlier, talker.method(:sayYourName).meta would
>>>work.
>>
>>No, it doesn't.  Method instances are not suited to carrying meta data:
> 
> [snip]
> 
>>The reason is that Method instances are created on each request:
> 
> Hmm, that's interesting. Good to know of it. So then methods are not
> objects per se, they just can be objectified.
> 
> Then really talker.meta[:sayYourName][:author] is the way to go. Of
> course, if the metadata is not intended/needed to be instance-specific,
> then it's better to be appended to the class.
> 
> Csaba

Thank's to all replies.

I've understood now the problem.

-

The Ruby Object Model does not contain reflective MetaClasses, which 
would enable to apply metadata even to methods.

-

I would like to know how a class which i've defined is represented in 
memory, and how I can access it.

-

A Visual representation of the Relevant Ruby Object Model (e.g. with 
UML) would be very helpfull to understand this immediately.

..

-- 
http://lazaridis.com