diff options
| author | git <svn@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2019-06-26 01:53:19 +0900 |
|---|---|---|
| committer | git <svn@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2019-06-26 01:53:19 +0900 |
| commit | dd57442f74024af465a16b7e19a34d0fc8533a53 (patch) | |
| tree | 5f1bd75e86f9dd249020d6c2b15f163a0895785c /doc/syntax/assignment.rdoc | |
| parent | 0bd5f846df2f6268f653773e0cd4a20e2a944646 (diff) | |
* remove trailing spaces.
Diffstat (limited to 'doc/syntax/assignment.rdoc')
| -rw-r--r-- | doc/syntax/assignment.rdoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/syntax/assignment.rdoc b/doc/syntax/assignment.rdoc index 08ee6096ef..2e2661c7a3 100644 --- a/doc/syntax/assignment.rdoc +++ b/doc/syntax/assignment.rdoc @@ -115,7 +115,7 @@ Using +eval+ to evaluate Ruby code will allow access to local variables in the same scope, even if the local variables are not assigned until after the call to +eval+. However, local variables assigned inside the call to +eval+ will not be reflected in the surrounding scope. Inside the call to +eval+, -local variables in the scope and local variables assigned inside the call to +local variables in the scope and local variables assigned inside the call to +eval+ will be accessible. However, you will not be able to access local variables assigned in previous or subsequent calls to +eval+ in the same scope. Consider each +eval+ call a separate nested scope. Example: |