From: "kddnewton (Kevin Newton) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "kddnewton (Kevin Newton)" <noreply@ruby-lang.org>
Subject: [ruby-core:117375] [Ruby master Bug#20400] Nested BEGIN{} execution order
Date: Fri, 29 Mar 2024 11:55:29 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-107534.20240329115529.10206@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20400.20240328181335.10206@ruby-lang.org
Issue #20400 has been updated by kddnewton (Kevin Newton).
Status changed from Open to Closed
Thank you for the clarification!
----------------------------------------
Bug #20400: Nested BEGIN{} execution order
https://bugs.ruby-lang.org/issues/20400#change-107534
* Author: kddnewton (Kevin Newton)
* Status: Closed
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
Right now there are specs for the order in which `BEGIN{}` should be executed, which is the order they appear in the file. For example:
```ruby
BEGIN { print "1" }
print "4"
BEGIN { print "2" }
print "5"
BEGIN { print "3" }
```
should output "12345". However, I couldn't find any tests/specs on what happens when `BEGIN{}` is nested. The order appears to be somewhat confusing, so I wanted to clarify if it was intentional or a bug. For example:
```ruby
BEGIN {
print "1"
BEGIN { print "2" }
}
```
prints "21", and:
```ruby
BEGIN {
print "1"
BEGIN { print "2" }
BEGIN { print "3" }
}
```
prints "231", and finally:
```ruby
BEGIN {
print "1"
BEGIN {
print "2"
BEGIN { print "3" }
}
BEGIN { print "4" }
}
```
prints "3241". Is this intentional?
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
prev parent reply other threads:[~2024-03-29 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 18:13 [ruby-core:117366] [Ruby master Bug#20400] Nested BEGIN{} execution order kddnewton (Kevin Newton) via ruby-core
2024-03-29 5:37 ` [ruby-core:117373] " nobu (Nobuyoshi Nakada) via ruby-core
2024-03-29 11:55 ` kddnewton (Kevin Newton) via ruby-core [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-107534.20240329115529.10206@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).