@no: "I recently published the OneWire module, which wraps parts of
the Dallas/Maxim Onewire API (for their IButton hardware),
see <<url>
The extension DLL/shared library is called "onewire", but I
also have some Ruby code that extends the same OneWire module.
I tried to name it "onewire.rb", which has "require onewire.so",
but the loader gets confused and only loads the DLL, not the
Ruby module (then the DLL),
What's the preferred way to handle this naming conflict? I'd
rather not rewrite the Ruby in C, and I'd prefer to avoid
renaming the DLL. Is there a third alternative?
Clifford Heath."
    @nobuyoshinakada: "Hi,
At Mon, 22 Aug 2005 20:16:18 +0900,
Clifford Heath wrote in [ruby-talk:153215]:
<quote>
Requiring with explicit ".so" suffix should load an extension
library even if ".rb" version is loaded already.
What does happen exactly at `require "onewire.so"', LoadError,
just false returns, or something else?
And where do you put them?
Nobu Nakada"
    @no: "<quote>
I think I made the mistake of putting the .so in the top
level directory where the .rb file was, instead of under
i386... Seems to work correctly now, sorry to bother you all."
{'source': 'USENET', 'other_information': '{"reply_count": 2, "forum_name": "comp.lang.ruby.20141021.mbox"}', 'file': 'data/output/usenet-comp.lang.parquet'}