From: Rich Lane <rlane@club.cc.cmu.edu>
To: Ben Walton <bwalton@artsci.utoronto.ca>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH] Remove use of Object tap method
Date: Wed, 03 Mar 2010 13:12:01 -0500 [thread overview]
Message-ID: <1267639869-sup-1568@zyrg.net> (raw)
In-Reply-To: <1267569917-sup-8028@pinkfloyd.chass.utoronto.ca>
Excerpts from Ben Walton's message of 2010-03-02 17:46:17 -0500:
> Excerpts from rick.tessner's message of Tue Mar 02 17:10:15 -0500 2010:
>
> > What about adding a lib/sup/tap.rb that looks like this:
>
> Or putting that directly in the lib/sup/util.rb that already has
> monkey patching type code? I'm ok with this solution and agree that
> the tap method is a beautiful little thing.
What do you think about requiring the backports gem and getting rid of
the compatibility code in util?
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-03-03 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 19:20 Ben Walton
2010-03-02 22:10 ` rick.tessner
2010-03-02 22:46 ` Ben Walton
2010-03-03 18:12 ` Rich Lane [this message]
2010-03-03 18:25 ` Ben Walton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1267639869-sup-1568@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=bwalton@artsci.utoronto.ca \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox