From: Christoph <chr_mail@...>
Date: 2003-11-22T22:35:52+09:00
Subject: Re: "stereotyping" (was: Re: Strong Typing (Re: Managing metadata about attribute types) )

Yukihiro Matsumoto wrote:
...
> The only reason the result is _not_ available from post 
> method is we don't have neat syntax construct.  Any proposal?

Ruby's default argument mechanism makes it impossible to add
the ``main return'' value as an extra argument of a post method,
so we need to offer the access to the ``main return'' value via a 
method or a variable automatically provided for every post method.

Since ``super'' is freely available we could use it (super with no arguments
allowed) - of course this is  ``old school keyword overloading'' which
I don't like too much,  so I probably would opt for another keyword 
like  ``main:result'',  ``main_result'', ``post:result'' or ``post_result''
(we could use the same keyword to provide access to the ``main return''
value in a wrap method).  

One way or the other, I really really want to have this feature even
at the cost of ugly syntax or keyword overloading. Any chance we 
got to play with this in 1.9? I am also wandering about your planning on
the interaction of blocks with the pre,wrap,post mechanism.
    
/Christoph