| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.

View
 

Design20080604

Page history last edited by Eric Hodel 12 years, 2 months ago

 Attendees:

  • Evan Phoenix
  • Charles Oliver Nutter
  • Brian Ford
  • matz
  • ko1

 

Time/Date/Location: 

11am June 5th JST, 7pm June 4th PDT, #ruby-core

 

Agenda

  • Named captures into local variables in 1.9 
  • Adding a formal/official annotation syntax, such as Python has. (Charles Nutter)
  • IO buffer behavior is specification or implementation detail?
  • Standardize the contents of RUBY_PLATFORM (Brian Ford)
  • Can all implementations agree to follow MatzRuby on RUBY_VERSION and RUBY_PATCHLEVEL? (Brian Ford)
  • No behavior changes (only bug fixes) in RUBY_PATCHLEVEL (Brian Ford)
  • Maintainance benchmark suits (ko1)
  • Subject prefix of ruby-core ML ([ruby-core:xxxx] YYYY) (ko1)
  • Protocol to deal with security issues. If security issue reported against MRI, sometimes it also applies to other implementations, but we don't know that until the official disclosure from MRI, which is some cases too late (JRuby item) 

 

Notes

  • RubyGems 1.2 will have operating system and RUBY_ENGINE defaults files to allow packagers and ruby implementers to override RubyGems defaults.  RubyGems will first attempt to load rubygems/defaults/operating_system.rb and rubygems/defaults/#{RUBY_ENGINE}.rb.  Feedback is still needed from implementers on additional RubyGems APIs to support necessary customizations. 

 

Action Items

  • Evan will email ruby-core with list of IO specs that have what appears to be impl. specific behavior 

 

Log

 ruby-core-20080604.txt

 

 

Comments (0)

You don't have permission to comment on this page.