[#119132] Segfault using ruby C on MacOS (Intel Catalina and M2 Sonoma) — "martin.kufner--- via ruby-core" <ruby-core@...>
Hey guys,
4 messages
2024/09/12
[#119133] Re: Segfault using ruby C on MacOS (Intel Catalina and M2 Sonoma)
— "martin.kufner--- via ruby-core" <ruby-core@...>
2024/09/12
I just saw, that the #includes dont show up in the c file ...
[#119145] [Ruby master Misc#20728] Propose Eileen Uchitelle as a core committer — "kddnewton (Kevin Newton) via ruby-core" <ruby-core@...>
Issue #20728 has been reported by kddnewton (Kevin Newton).
14 messages
2024/09/12
[#119312] [Ruby master Bug#20762] `make test-basic` with -DRGENGC_FORCE_MAJOR_GC is always failure — "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@...>
Issue #20762 has been reported by hsbt (Hiroshi SHIBATA).
6 messages
2024/09/27
[ruby-core:119286] [Ruby master Feature#20759] No good API to query which parser is being used
From:
"luke-gru (Luke Gruber) via ruby-core" <ruby-core@...>
Date:
2024-09-24 18:17:29 UTC
List:
ruby-core #119286
Issue #20759 has been reported by luke-gru (Luke Gruber). ---------------------------------------- Feature #20759: No good API to query which parser is being used https://bugs.ruby-lang.org/issues/20759 * Author: luke-gru (Luke Gruber) * Status: Open ---------------------------------------- Right now the best way I found is: ```ruby parser = RUBY_DESCRIPTION =~ /prism/i ? "prism" : "parse.y" ``` This is useful if you want to invoke a subprocess with the same options given to ruby. ARGV parsing might not work because the option might have been given via RUBYOPT. Maybe `RubyVM::PARSER` could be used? -- 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/lists/ruby-core.ml.ruby-lang.org/