From: Austin Ziegler <halostatue@...>
Date: 2006-04-06T21:28:46+09:00
Subject: Re: un_include and un_extend

On 4/6/06, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:> In message "Re: un_include and un_extend">     on Wed, 5 Apr 2006 09:03:47 +0900, "itsme213" <itsme213@hotmail.com> writes:>| Thanks. Will 2.0 allow this?> No plan.  Currently I have no reason to allow it.
I'd love to change your mind about that. One reason isTransaction::Simple. My preferred use of Transaction::Simple will notbe including it into a class, but extending an object with it like so:
  foo = "mystring"  Transaction::Simple.start(foo) do |t_foo|    t_foo.gsub!(/my/, "your")    t_foo.rewind_transaction    t_foo.gsub!(/string/, "test")  end  t_foo.start_transaction # I want *this* to throw an exception.
It would make certain things easier to manage in classes that useTransaction::Simple. I understand that it wouldn't be easy, and itwould be almost impossible to automate, so perhaps only allowing it onmodules that have an #unextended method?
I think that most modules are things that you only want to add to anobject or class. But I think that there are transient things whichwould benefit from this.
-austin--Austin Ziegler * halostatue@gmail.com               * Alternate: austin@halostatue.ca