PDA

View Full Version : Using both DIV32 and LONGs together



BrianT
- 9th January 2009, 07:27
I have many old code modules that uses DIV32. I have just tried to use the LONG compiler with some of these and I get an error message

ERROR: Macro DIV32?CW not found in macro file.

Does this mean I cannot use DIV32 with the long compiler or have I just got a bad setup.

Cheers
BrianT

BrianT
- 9th January 2009, 08:24
I renamed the PBP, PBPW and PBPL directories so that MCSP 3.0.0.5 could not immediately find PBPW.EXE then I did a new clean install from the PBP 2.50 CD.
I downloaded and ran the PBP250b.exe patch.

In the new PBP directory, just created by the new install, I can see PBP.EXE, PBPL.EXE and PBPW.EXE.

I pointed MCSP 3.0.0.5 to the new directory C:\PBP.

I reckon that should be a 'new and clean' install.

I can clear the PBPL box and my code compiles. This code has no LONG variables declared. When I check the "use PBPL" box and try to compile, I get the error message ....ERROR: Macro DIV32?CW not found in macro file.

I really don't want to have to recode all the subroutines that use DIV32 as there are many of them.

Can anyone confirm they can use the PBPL compiler with code that has DIV32 instructions in it?

Cheers
BrianT

Acetronics2
- 9th January 2009, 08:42
Hi, Brian

NO WAY to use DIV32 with PBPL ( one could say : Why ??? )

you want to use a function that does NOT exist in PBPL !!!

a simple text editor will help you more than you think ...


Alain

BrianT
- 9th January 2009, 08:56
Bugger.
Page 38 (PBP manual 7/07) says .... DIV32 is not supported by PBPL....

That means a huge job of converting all my old code that uses DIV32.

I need the extra accuracy of PBPL and did not expect to have to rewrite old subroutines that have been extensively debugged over the past several years.

Sadly
BrianT

Acetronics2
- 9th January 2009, 12:46
Example of the "huge job" ( lol ), here :

http://www.picbasic.co.uk/forum/showpost.php?p=62024&postcount=149

... please, stop kidding ...

Alain

PS:


that have been extensively debugged


Was so much bugged ??? ...