From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 384FD1960007 for ; Fri, 19 Jun 2015 03:49:20 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (smtp.nagaokaut.ac.jp [133.44.2.201]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id A2021B5D8A9 for ; Fri, 19 Jun 2015 04:12:09 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (localhost.nagaokaut.ac.jp [127.0.0.1]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id F0BA697A847 for ; Fri, 19 Jun 2015 04:12:09 +0900 (JST) X-Virus-Scanned: amavisd-new at nagaokaut.ac.jp Authentication-Results: funfun.nagaokaut.ac.jp (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=sendgrid.me Received: from funfun.nagaokaut.ac.jp ([127.0.0.1]) by funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUCwj5GQUVyC for ; Fri, 19 Jun 2015 04:12:09 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 5D9DC97A846 for ; Fri, 19 Jun 2015 04:12:09 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id E8E1A95243E for ; Fri, 19 Jun 2015 04:12:08 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 495DD120476; Fri, 19 Jun 2015 04:12:06 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o10.shared.sendgrid.net (o10.shared.sendgrid.net [173.193.132.135]) by neon.ruby-lang.org (Postfix) with ESMTPS id 24F0F120434 for ; Fri, 19 Jun 2015 04:12:02 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=Qz6/LDYz+NzqGEDp3OoNKL7zago=; b=t6yGdIVS8fZCQI9fwT +ZmriT64xcDLTb2FEvdCk9t3++evqL9Gl6YZQpGZuY3W1pm5DAPKK9vSiaMHzEK8 YWO05EqVN0o9XrZHS39hyCOiTWMSY8vl7Uy0vJF5esxuu53ZTkLXJ+7GAAd8Jxfn 2Tu9fmF5UdujxEWJfehRx9ZvM= Received: by filter0571p1mdw1.sendgrid.net with SMTP id filter0571p1mdw1.9163.558317FC1D 2015-06-18 19:11:57.86904659 +0000 UTC Received: from ismtpd-016.iad1.sendgrid.net ([UNAVAILABLE]. [10.42.2.110]) by 10.42.243.12:2500 (trex/5.2.13); Thu, 18 Jun 2015 19:11:58 GMT Received: from herokuapp.com (ec2-23-20-144-76.compute-1.amazonaws.com [23.20.144.76]) by ismtpd-016 (SG) with ESMTP id 14e0815b69c.5b69.feb8e Thu, 18 Jun 2015 19:11:57 +0000 (UTC) Date: Thu, 18 Jun 2015 19:11:57 +0000 From: funny.falcon@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Redmine-MailingListIntegration-Message-Ids: 44213 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11283 X-Redmine-Issue-Author: nepalez X-Redmine-Sender: funny_falcon X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS4D8rdTbWZ4ub28JCiOJFHWpJJmZy+rDrcy8x Q/ptsFhXpJfnKfIt5EbuqeQKDnyxbXRJKXx2694oXCP90Gu+KT764eUnD8R2xFifaldvwLxEKWLOka cEx2kny1Q5npclKgTFh6A8oUF/SitaQoJhvB X-ML-Name: ruby-core X-Mail-Count: 69664 Subject: [ruby-core:69664] [Ruby trunk - Bug #11283] Block assigned implicitly X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #11283 has been updated by Yura Sokolov. This is "hidden feature", not the bug: `Proc.new` can consume unnamed block passed to method. It makes possible following code: ````ruby def do_now_or_later if can_do_now? yield else do_it_later Proc.new end end do_now_or_later { puts 'hi' } ```` In your case block is passed to implicit `Proc.new` in the implementation of `define_method`. I agree, that it is a bit weird feature. ---------------------------------------- Bug #11283: Block assigned implicitly https://bugs.ruby-lang.org/issues/11283#change-53025 * Author: Andrew Kozin * Status: Open * Priority: Normal * Assignee: * ruby -v: 1.9.3, 2.0, 2.1, 2.2, ruby-head * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- That is how it works: module Test def self.build(&block) klass = Class.new(Object) klass.__send__(:define_method, :foo) klass.__send__(:define_method, :bar) klass end end Tested = Test.build { :foo } # warning: tried to create Proc object without a block # => Tested Tested.new.foo # => :foo Tested.new.bar # => :foo The block is assigned to all calls to `:define_method` via `Object#__send__` implicitly, while it wasn't asked to. The behaviour is tested under MRI 1.9.3, 2.0, 2.1, 2.2, ruby-head. It doesn't occur under rbx-2 and jruby (1.7, 9.0.0.0). For the context look at this thread https://github.com/mbj/mutant/issues/356 -- https://bugs.ruby-lang.org/