Clifford Heath wrote:
> I recently published the OneWire module, which wraps parts of
> the Dallas/Maxim Onewire API (for their IButton hardware),
> see <http://onewire.rubyforge.org/>.
> 
> 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.

Hmmm...RMagick does exactly what you describe: RMagick.rb loads 
RMagick.so. I'm not sure why RMagick would work and onewire wouldn't.