From 8f8f92b508e48fe16c584cea9a8b819d72118342 Mon Sep 17 00:00:00 2001 From: hsbt Date: Wed, 30 Dec 2015 11:26:09 +0000 Subject: [PATCH] * doc/syntax/calling_methods.rdoc: fix old operator for safe navigation operator. [ci skip][fix GH-1182] Patch by @dougo git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@53385 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- ChangeLog | 5 +++++ doc/syntax/calling_methods.rdoc | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index d74af376fd..7152c2c06c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +Wed Dec 30 20:25:52 2015 SHIBATA Hiroshi + + * doc/syntax/calling_methods.rdoc: fix old operator for safe navigation + operator. [ci skip][fix GH-1182] Patch by @dougo + Wed Dec 30 16:43:23 2015 Kuniaki IGARASHI * test/ruby/test_string.rb (test_ord): Add test for String#ord. diff --git a/doc/syntax/calling_methods.rdoc b/doc/syntax/calling_methods.rdoc index f1ebf186f7..ec86ef05ee 100644 --- a/doc/syntax/calling_methods.rdoc +++ b/doc/syntax/calling_methods.rdoc @@ -27,7 +27,7 @@ This sends the +my_method+ message to +my_object+. Any object can be a receiver but depending on the method's visibility sending a message may raise a NoMethodError. -You may use .? to designate a receiver, then +my_method+ is not +You may use &. to designate a receiver, then +my_method+ is not invoked and the result is +nil+ when the receiver is +nil+. In that case, the arguments of +my_method+ are not evaluated.