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:
>
Only now (after entering the ticket) I do see this and understand some
(well, hardly anything) of it.
But if I can test any modified rexx.exe: I'll be happy to do so
Walter
Von: Rick McGuire [mailto:object.r...@gmail.com]
Gesendet: Montag, 23. Dezember 2013 14:23
An: Open Object Rexx Develop
Rick, You MAY have an idea where the problem is and I'd be more than happy
to test if the fix, if any, solves the problem.
I have created ticket 1229 with less information than you require.
Mind you: it's not my baby at all.
But it may be a start.
Walter
Von: Rick McGuire [mailto:object.
Well, it's more than just a good idea. Until I have details on how to
recreate the problem, I have no way of verifying if I've fixed the problem.
As I keep reminding Walter, entering a bug report is the only way to
report a bug and get it fixed.
Rick
On Mon, Dec 23, 2013 at 8:25 AM, Mike Cowli
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:
Well, until a bug report is created with details on how to recreate the problem,
it is not going to get worked on.
and
The problem appears to be that ooRexx 4.2.x is unable to find an
application function registered with RexxRegisterFunctionExe. "
Is it now too late to fix it in 4,2?
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
Well, until a bug report is created with details on how to recreate the
problem, it is not going to get worked on.
Rick
On Mon, Dec 23, 2013 at 1:27 AM, Walter Pachl
wrote:
> I got this background from Mark H
>
> "A THE macro containing a call to the inprefix() function worked fine
> with ooRex
