After a long trip, I decided to reopen the OA32 homepage at the same provider under the following address http://objasm32.tripod.com/
All other URLs will be erased in the next time. I beg you to update your links...

Regards,

Biterider
Posted on 2004-05-27 08:05:06 by Biterider
Glad to see a positive outcome .. for the moment ?
Posted on 2004-05-27 08:53:26 by Homer

Just a small question :
When I have OOP_Init PRIMER_ONLY DEBUG then masm told that " conflicting parameter definition in HexDump" in Debug.inc .
But if I change name of HexDump to OHexDump then evrything ok. Have HexDump been called automatically in debug state ? If I changed HexDump macro name , whether it make effect to program ?
I'm using MASM SP1


Hello DreamWeaver,

Im sorry for such a late reply, but I now see the problem your addressing here. It stems from the fact that Hutch added to his MASM32.LIB in the latest Masm release a function called "HexDump". I wrote this function well before this new version of MASM32.LIB, but it was still part of the masm package itself (in VKim's debug libraries). I dont think it was an oversite either, as the VKim package that come with the latest version has its Debug.inc modified by renaming this function such it doesnt conflict.

Myself, I tend not to upgrade my Masm32 package too often cause i have my Windows.inc tweeked the way i like it ;) . However, i just did, and this problem came to the forground very quickly.

Since it would be more hassle to modify the MASM32.LIB, its probably best to modify the Debug.inc that comes with the ObjAsm32 package. Since i define the fucntion directly inside Debug.inc, i would suggest renaming it to "HexDump2". As well in the DumpMem macro (approximately line 1048) rename its invoke call to HexDump2.

This should fix your problem. Again, sorry for the delay on this, but we really didnt have any clue untill I upgraded to the Masm32 v8 package.

For the future releases, we are planning to develop a separete OOP debugging window, with OOP specific tools for debuging built in. This will hopefully keep this sort of problem from happening, as we will redesign from the ground up to produce a separate debug lib that works very similar to VKim's model.


Regards,
:NaN:
Posted on 2004-05-28 01:15:25 by NaN