enebo[m] has quit [Ping timeout: 246 seconds]
makePar[m] has quit [Ping timeout: 246 seconds]
makePar[m] has joined #jruby
enebo[m] has joined #jruby
lucerne has quit [Read error: Connection reset by peer]
lucerne has joined #jruby
lucerne has quit [Ping timeout: 255 seconds]
lucerne has joined #jruby
lucerne has quit [Ping timeout: 252 seconds]
lucerne has joined #jruby
lucerne has quit [Ping timeout: 252 seconds]
lucerne has joined #jruby
subbu has joined #jruby
subbu has quit [Ping timeout: 255 seconds]
subbu has joined #jruby
yosafbridge has quit [Quit: Leaving]
<byteit101[m]> Why do we use dlopen vs System.load() in jnr?
subbu has quit [Quit: Leaving]
yosafbridge has joined #jruby
lucerne has quit [Read error: Connection reset by peer]
<headius> I think because we can't control the way the latterr loads stuff
<headius> But that's a decision made before I took over maintenance
<byteit101[m]> Ok, so JNA also uses dlopen, and all instances of system.load are JNI-specific as far as I can find
<byteit101[m]> None of those libraries will work for us
<byteit101[m]> and further, we must have some changes in jruby itself to at least convert uri:classloader: to a) a jar:! url, or b) to use a custom resource
<byteit101[m]> do you know why jnr/jffi StubLoader is only called reflectively?