From: Trans <transfire@...>
Date: 2006-12-07T02:54:39+09:00
Subject: Re: invasive parameters as method mode variables


James Edward Gray II wrote:
> On Dec 6, 2006, at 9:49 AM, Trans wrote:
>
> > Thouhgts?
>
> My thoughts on your current suggestion:  Yuck.  You really want this
> to become so common that the language itself supports it?  I
> definitely don't.  The whole usage case is a code smell, in my opinion.

perhaps. just exploring the idea. certainly Binding.of_caller allows
this kind of thing more or less. and I think there are good occassions
to use Binding.of_caller. in this case the no_multi_key option would
rarely be used. so having to turn the whole thing into a class, as ara
suggests, for one (or two) uncommon parameter seems like overkill,
although maybe it is better to do so.

I did think of one other way it could be done, inspried by an idea _why
had long ago:

  #

  def no_multi_flag
    class << self
      def multi_flag(argv); argv; end
    end
    yield
    class << self
      undef_method :multi_flag
    end
  end

though that sort of smells worse in my opinion.

> My thoughts on your suggestions in general:  You sure spend a lot of
> time trying to rewrite Ruby's syntax.  ;)

I know. It's sort or a hobby of mine. I have a general interest in
understanding the human <-> programming language interface.

T.