From: "alanwu (Alan Wu)" Date: 2022-06-21T22:09:02+00:00 Subject: [ruby-core:109036] [Ruby master Misc#18836] DevMeeting-2022-07-21 Issue #18836 has been updated by alanwu (Alan Wu). * [Bug #18780] Surprising `self` for C API `rb_eval_string()` (alanwu) * Script for `rb_eval_string()` runs with locals from the inner most Ruby context, but `self` is always top level `self` (`main`). This unique execution environment is surprising; it's not equivalent to any environment one could get using pure Ruby. * Test script available at [[ruby-core:108919]](http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/108919). You need to flip the `if` in the C code to see it. * `extension.rdoc` says it's [supposed to capture local variables](https://github.com/ruby/ruby/commit/9562813d338b5f2870408e95747d71502590c14f#diff-756b839706deff86d7d27012df24a9df5105960cf6a23d9fa96f3fe3a53acd7cR305) while the header says it runs in an ["isolated binding"](https://github.com/ruby/ruby/blob/fdd1102550d375be4302ac8d2e081797de00a205/include/ruby/internal/eval.h#L43) * It looks like `self` has stayed as the top level `self` [since 1.3](https://github.com/ruby/ruby/blob/ruby_1_3/eval.c#L1119) * Should we change `self` for scripts passed to `rb_eval_string()`? ---------------------------------------- Misc #18836: DevMeeting-2022-07-21 https://bugs.ruby-lang.org/issues/18836#change-98153 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2022/07/21 13:00-17:00** (JST) Log: *TBD* - Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker. - Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly. - Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue). - We will write a record of the discussion in the file or to each ticket in English. - All activities are best-effort (keep in mind that most of us are volunteer developers). - The date, time and place of the meeting are scheduled according to when/where we can reserve Matz's time. - *DO NOT* discuss then on this ticket, please. # Call for agenda items If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format: ``` * [Ticket ref] Ticket title (your name) * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.) ``` Example: ``` * [Feature #14609] `Kernel#p` without args shows the receiver (ko1) * I feel this feature is very useful and some people say :+1: so let discuss this feature. ``` - It is recommended to add a comment by 2022/07/18. We hold a preparatory meeting to create an agenda a few days before the dev-meeting. - The format is strict. We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). We may ignore a comment that does not follow the format. - Your comment is mandatory. We cannot read all discussion of the ticket in a limited time. We appreciate it if you could write a short summary and update from a previous discussion. -- https://bugs.ruby-lang.org/ Unsubscribe: