Article # 635, added by Geoworks, historical record
| first | previous | index | next | last |

Hex number format in source files.



Q. I have a .ui file has these lines:

	gstring {
		GSBeginString
		GSDrawBitmapAtCP <(EndInkTestLCIcon-StartInkTestLCIcon)>
		StartInkTestLCIcon label byte
		Bitmap <64,40,BMC_PACKBITS, mask BMT_MASK or BMF_4BIT>
		db	0feh, 000h, 001h, 00fh, 0c0h, 0feh, 000h
		db	0f3h, 0ddh, 002h, 070h, 000h, 007h, 0f2h, 0ddh
		......

   When I do mkmf, CPP32.EXE complains "Error : incorrect
   number format". If I change the numbers to 0xnn, the error goes away.

   If I do "set cpp=cpp.exe" before running mkmf, it can handle 0nnh
   format without error. Is this the expected behavior?

A. This is a problem when the Borland preprocessor is used instead of
   uicpp.exe for processing .ui files. The Borland preprocessor does
   more than just process '#' directives: it inserts spaces around the
   numbers, for an unknown reason, which ESP then chokes on.
   I don't know why mkmf is using bcc32 instead of uicpp.