Hacker Newsnew | past | comments | ask | show | jobs | submit | tumbledoor's commentslogin

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.


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


A segfault from running interpreted code is definitely an MRI bug.


Unless there are third party C extensions involved.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: