From: matz@... (Yukihiro Matsumoto)
Date: 2001-10-26T06:32:16+09:00
Subject: [ruby-talk:23357] Re: Ruby macros

Hi,

In message "[ruby-talk:23262] Re: Ruby macros"
    on 01/10/25, Avi Bryant <avi@beta4.com> writes:

|When a few of
|us were talking about this at RubyConf, Dave Thomas proposed a
|construct where the "is" keyword would pass the preceding syntactic
|element to whatever method followed it - ie,
|
|class A; end is foo
|
|would more or less trigger:
|
|foo("class A; end")

It was interesting.  But I couldn't think of "exact" behavior of "is".
It should do something at compile time, since it sometimes works like
macro; at the same time, it have to do other things in run time too,
since it sometimes works like assertion.

Would somebody come up with the proposal of "is" behavior in the
detail level of PEP(Python)/RFC(Perl)?  I'm afraid that it may result
as total redefinition of Ruby internal behavior.

							matz.