3 ms·

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 shoul

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.

masklinn 12y ago
> 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?
stormbrew 12y ago
A segfault from running interpreted code is definitely an MRI bug.
- seivadmas 12y ago
  Unless there are third party C extensions involved.