Hi,
On 2010.04.23 20:45, Pritpal Bedi wrote:
I am just asking, which ChangeLog entry after 15 Mar highlighted this difference.
Any. Any entry can change code size, this affect memory allocation, addresses of functions, and makes bug be visible or hidden.
Based on this alone, I am about to remove a lot of INLINE calls from hbXBP.
It's good practice to save one more Harbour VM stack frame, but it has nothing to GPF.
I already told, I have removed all calls to inline access/assign and everything is working fine without changing anything in other C code.
So, you've just hidden the bug instead of trying to find it. One more time bomb. Try to not forget about this change. It is possible that after two years you'll be able to "solve" one more (actually the same) GPF problem by reintroducing INLINE methods :)
Regards, Mindaugas _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
