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 614C1196000C for ; Fri, 19 Jun 2015 14:27:10 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [133.44.2.201]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id B7F34B5D997 for ; Fri, 19 Jun 2015 14:50:04 +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 6999C97A82B for ; Fri, 19 Jun 2015 14:50:06 +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 6nIDgFpr_OgM for ; Fri, 19 Jun 2015 14:50:06 +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 EB5BB97A826 for ; Fri, 19 Jun 2015 14:50:05 +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 1A4AA952439 for ; Fri, 19 Jun 2015 14:50:03 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id D5DBE12047A; Fri, 19 Jun 2015 14:50:00 +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 5403E12046C for ; Fri, 19 Jun 2015 14:49:57 +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=1GI/A6lPeypJZQmPkOO9JyUwrVE=; b=muJHsb8vZMmrCyDfPG bBDs/8Lg+/YcR80+pAFjR2olBsVrWXHGQOsfqxUm3HmzpPNbkip+THBovbmV558s OFLoMU1Y6MM88FkAnMq+JjWkbceu6JZ9oOm7kW/KQcLlFecwgTti6Hxb81aB7a26 uQxMi6muEisr2zLFKYg3yXp6c= Received: by filter0609p1mdw1.sendgrid.net with SMTP id filter0609p1mdw1.31629.5583AD7D14 2015-06-19 05:49:52.658191832 +0000 UTC Received: from herokuapp.com (ec2-54-162-203-126.compute-1.amazonaws.com [54.162.203.126]) by ismtpd-046 (SG) with ESMTP id 14e0a5dbe87.6f3b.2a986c Fri, 19 Jun 2015 05:49:52 +0000 (UTC) Date: Fri, 19 Jun 2015 05:49:52 +0000 From: andrew.kozin@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: 44224 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11283 X-Redmine-Issue-Author: nepalez X-Redmine-Sender: nepalez 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS6ArIrUwt9nM1DushCM6VDtfxDiWLtNfhxXbz Y4xrw6aq3QTWtwr12KAGv4WThWkdm5zB/CehUCQZDUWzmsh2gGa/LYGgwpYhvIERpvFPiQbt2iy0da jyoaxjUMjalsSHNbuAUrP0/2JC8wPCSp8fjD X-ML-Name: ruby-core X-Mail-Count: 69674 Subject: [ruby-core:69674] [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 Andrew Kozin. Not, in my examples (from the initial post) it does not do that, but something different. Namely, it doesn't assigning a **new** proc (that would be OK) Instead, the interpreter it looks around in search **what else** it could use when I doesn't send a proc, then takes what it found somewhere and pushes it to the method. MRI doesn't let me decide whether the method should be called without a proc (that should be interpreted as asking for `Proc.new`, as in your example). **This** is the bug, not the way it works out the `:define_method` call. ---------------------------------------- Bug #11283: Block assigned implicitly https://bugs.ruby-lang.org/issues/11283#change-53034 * 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/