| 
  • 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
 

Design20080430

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

 

Ruby Design Meeting: 2008-04-30 PDT

 

Attendees:

  • Ola Bini
  • Thomas E Enebo
  • Charles Oliver Nutter
  • MenTaLguY
  • Laurent Sansonetti
  • Evan Phoenix
  • Brian Ford
  • Yukihiro Matsumoto

 

Time/Date/Location: 

11am May 1st, 2008 JST (April 30th, 2008 7pm), #ruby-core

 

Agenda

  • Scheduling of next meeting
    • Consider EU timezone issue
  • Action item review
  • Integration of RubySpecs into MRI/trunk and MRI/1.8
  • Continuous integration, regression testing for Ruby 1.8 branch releases (e.g. 1.8.7)
    • valgrind
  • MacRuby and other syntax changes
  • Scheduling: sleep intervals and system clock changes
    • Sleep time with Ruby select/sleep behaves erratically when system clock is changed
    • Easiest remedy is to use clock_gettime(CLOCK_MONOTONIC), when available, in place of gettimeofday() in the main select loop
    • Stable sleep times are required to correctly implement facilities like Java's DelayQueue in Ruby
    • Patch in ruby-core:15066
  • String class in 1.9 & bytestrings
  • Uninclude functionality
  • Include on Classes
  • RUBY_ENGINE or similar constant to indicate implementation

 

 

Notes

  • Decided on next meeting, to be held same time of day. 11am May 16th JST, 7pm May 15th PST. 

 

Action Items

  • Email ruby-core concern spec split off repo 
  • Discuss syntax semantic mapping (MacRuby related) on ruby-core
  • MentalGuy will find the patch for 1.8/1.9 to use the monotonic clock if available
  • Evan will bring up running program name (RUBY_BIN_PATH in Rubinius) on ruby-core

 

Log

 ruby-core-20080430.txt

 

Comments (0)

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