News for hackers. Stuff that matters.
Re:MRI Developers Don't Use RubySpec and It's Hurting Ruby by tumbledoor on Wednesday December 31, 2014 @07:19PM (#8821700)
If MRI fails RubySpec specs, and the MRI developers didn't write those specs, is that a bug in RubySpec or MRI?

It's egotistical because he's saying they should make their project conform to his third party specification.

Re:MRI Developers Don't Use RubySpec and It's Hurting Ruby by masklinn on Wednesday December 31, 2014 @07:27PM (#8821720)
> If MRI fails RubySpec specs, and the MRI developers didn't write those specs, is that a bug in RubySpec or MRI?

If the specs were written based on (and working in) a previous MRI version, how can it be anything but an MRI bug? Especially when previously working code segfaults?

> It's egotistical because he's saying they should make their project conform to his third party specification.

How could he do anything but a third-party specification when the first-party refuses to produce a specification?

Re:MRI Developers Don't Use RubySpec and It's Hurting Ruby by stormbrew on Wednesday December 31, 2014 @07:40PM (#8821752)
A segfault from running interpreted code is definitely an MRI bug.
Re:MRI Developers Don't Use RubySpec and It's Hurting Ruby by seivadmas on Thursday January 01, 2015 @12:23AM (#8822252)
Unless there are third party C extensions involved.