Re: [Oorexx-devel] THE Function registration problem

2013-12-23 Thread Mark Miesfeld
Rick, Reading your previous post I was going to reply that, on Windows, there is a reference count and MSDN says the library won't be unloaded until the count goes to 0. But, it looks like you've already seen that. ;-) -- Mark Miesfeld On Mon, Dec 23, 2013 at 5:41 AM, Rick McGuire wrote: >

Re: [Oorexx-devel] THE Function registration problem

2013-12-23 Thread Walter Pachl
Rexx Developer Mailing List Betreff: [Oorexx-devel] THE Function registration problem Still waiting for Walter to open a bug report on how to recreate the THE problem so I can verify, but I have a theory on what's going on here. I wrote some test cases and added them to the test suite fo

Re: [Oorexx-devel] THE Function registration problem

2013-12-23 Thread Rick McGuire
Ok, it looks like solution #1 will work. Both dlopen() and Windows LoadLibrary maintain reference counts, so it is possible to lock library in place if it needs to maintain a local copy. This could be a fairly simple fix (which can probably wait until Thursday). Rick On Mon, Dec 23, 2013 at 8:

[Oorexx-devel] THE Function registration problem

2013-12-23 Thread Rick McGuire
Still waiting for Walter to open a bug report on how to recreate the THE problem so I can verify, but I have a theory on what's going on here. I wrote some test cases and added them to the test suite for function EXE registrations, and they are definitely working. However, the information from M