Bug #9186: json/pure.rb missing on trunk

• Status: Rejected
• Assignee: naruse (Yui NARUSE)
• Target version: 2.1.0
• ruby -v: ruby 2.1.0dev (2013-11-30 trunk 43927) [x86_64-darwin13.0]
• Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN

Line 60 of ext/json/lib/json.rb requires json/pure if json/ext cannot be required.

This file is missing on trunk, meaning the JSON library is broken unless the C extension is present.

[hsbt (Hiroshi SHIBATA)]

• Assignee set to naruse (Yui NARUSE)
• Target version set to 2.1.0

[vo.x (Vit Ondruch)]

I'm just wondering, what should be the circumstances that C extension is missing?

@vo.x (Vit Ondruch): I noticed this because it was breaking on Rubinius - there's also probably some situations where C extensions can't be loaded in CRuby.

[kosaki (Motohiro KOSAKI)]

there's also probably some situations where C extensions can't be loaded in CRuby.

Hmm.. When? It shouldn't happen on CRuby.

Hmm.. When? It shouldn't happen on CRuby.

It isn't a common use case, but I have experienced some issues with C extensions when cross-compiling CRuby.

[kosaki (Motohiro KOSAKI)]

2013/12/1 charliesome (Charlie Somerville) [e-mail]:

Issue #9186 has been updated by charliesome (Charlie Somerville).

Hmm.. When? It shouldn't happen on CRuby.

It isn't a common use case, but I have experienced some issues with C extensions when cross-compiling CRuby.

Can you please elaborate more? Do you mean JSON is now cross-compile
unsafe? It seems horrible.

Can you please elaborate more? Do you mean JSON is now cross-compile unsafe? It seems horrible.

This was a long time ago, and I can't recall specific details. I was just using this as an example of when C extensions may not work properly and this bug could be triggered in CRuby.

[naruse (Yui NARUSE)]

• Status changed from Open to Rejected

I intentionally removed pure.rb on ruby's repo because CRuby always have C exts.

If C exts is not properly build, the binary shouldn't work.