Re: opening a window (a fix for EFFM)
Chris Bensler wrote:
>
> Did you try running the code on an Eu version < 2.5?
Yes. Actually I didn't try 3.1 at all.
> EFFM is likely a victim of the introduced function sidefx
At no point does EFFM, weird as some bits of it are, try the even weirder trick
of modifying the same thing on both the LHS and RHS of a single assignment
statement, at least not as far as I am aware. In any case the facts easily
disprove any such theory.
A machine error in a c_func(xHeapAlloc,{..}) call, cmiiw, means one and only one
thing: some memory corruption happened before.
The fact that it works on 3.1, and/or with the revised routines I posted just
means the corruption is subtle and that it works is a bit of a fluke.
Perhaps if the code I posted were extended to check say 512 dwords either side
for damage then the root cause of the problem would surface. However, intriguing
as this may be, imo the program is not worth salvaging; I'd personally rather
spend my time writing an arwen based version.
Regards,
Pete
|
Not Categorized, Please Help
|
|
