Adding the ExternC modifier was not enough (same error), however "ExternC
*const*" did the trick!
So probably the following should be added:
*ExternC #ifndef DELAYIMP_INSECURE_WRITABLE_HOOKS const #endif* PfnDliHook
__pfnDliFailureHook2
= delayFailHook;
Have to run (far too late,
This documentation for the hooks
https://msdn.microsoft.com/en-us/library/z9h1h6ty.aspx
Shows a different declaration for this variable. Try adding the ExternC
modifier. That change is building fine for me.
Rick
On Mon, May 1, 2017 at 5:44 PM, Rony G. Flatscher
wrote:
On 01.05.2017 23:40, Rick McGuire wrote:
> Try removing the int and see if it makes a difference.
Just tried it, no it does not make a difference, same error: redefinition,
different modifiers.
---rony
>
>
> On Mon, May 1, 2017 at 5:32 PM, Rony G. Flatscher
It works fine for me on 2013 version with or without the int.
Rick
On Mon, May 1, 2017 at 5:32 PM, Rony G. Flatscher
wrote:
>
> On 01.05.2017 23:10, Rick McGuire wrote:
>
> This has been encountered before. You need to have the correct level of
> the SDK installed.
Try removing the int and see if it makes a difference.
Rick
On Mon, May 1, 2017 at 5:32 PM, Rony G. Flatscher
wrote:
>
> On 01.05.2017 23:10, Rick McGuire wrote:
>
> This has been encountered before. You need to have the correct level of
> the SDK installed. Mark
This has been encountered before. You need to have the correct level of the
SDK installed. Mark Miesfeld always recommended this one:
http://www.microsoft.com/en-us/download/details.aspx?id=8442
Rick
On Sun, Apr 30, 2017 at 3:43 PM, Rony G. Flatscher
wrote:
> While
Rony, I'm successfully building ooRexx 5.0 (both 32- and 64-bit) with
Visual Studio 2015 (Community).
You might want to check the "How to build" documents I've written in our
ooRexx Wiki at https://sourceforge.net/p/oorexx/wiki/how-to-build-oorexx/
My version of \Program Files (x86)\Microsoft
On 01.05.2017 16:19, Rick McGuire wrote:
> If the parsing event handler is storing references to any of the proxy
> objects in other ooRexx
> objects (arrays, etc.), those objects will still be anchored. The uninits are
> definitely
> interleaved with execution in the sample program, so problems
Retested today quite exhaustively (see below), and indeed I cannot create any
Rexx crashes anymore,
which is *really* great!
---
However, retesting today, I just realized, that all the uninits only start to
run *after* the test
script ends!
Running the test script on the patched interpreter