[#85940] [Ruby trunk Bug#14578] Forking a child process inside of a mutex crashes the ruby interpreter — ben.govero@...
Issue #14578 has been reported by bengovero (Ben Govero).
3 messages
2018/03/05
[#86205] [Ruby trunk Feature#14618] Add display width method to String for CLI — aycabta@...
Issue #14618 has been reported by aycabta (aycabta .).
3 messages
2018/03/19
[#86366] Re: [ruby-cvs:70102] usa:r63008 (trunk): get rid of test error/failure on Windows introduced at r62955 — Eric Wong <normalperson@...>
usa@ruby-lang.org wrote:
3 messages
2018/03/28
[ruby-core:85927] [Ruby trunk Feature#4824] Provide method Kernel#executed?
From:
matthew@...
Date:
2018-03-04 23:40:19 UTC
List:
ruby-core #85927
Issue #4824 has been updated by phluid61 (Matthew Kerwin). dsferreira (Daniel Ferreira) wrote: > phluid61 (Matthew Kerwin) wrote: > > > For what it's worth, I think __main__ is best, or main? > > I would agree with `main` in the following way: > `__main__`, not **main**. Returns a boolean value, which can be used as a predicate: ~~~ruby if __main__ foo end ~~~ ---------------------------------------- Feature #4824: Provide method Kernel#executed? https://bugs.ruby-lang.org/issues/4824#change-70782 * Author: lazaridis.com (Lazaridis Ilias) * Status: Assigned * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) * Target version: ---------------------------------------- The current construct to execute main code looks not very elegant: ~~~ruby if __FILE__ == $0 my_main() # call any method or execute any code end ~~~ With a `Kernel#executed?` method, this would become more elegant: ~~~ruby if executed? #do this #do that my_main() end ~~~ or ~~~ruby main() if executed? ~~~ This addition would not break any existent behaviour. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>