ASM Community

Hutch--, there is no reason not to use my macro, which does much more. Check it out at Thomas's snippet library, and feel free to add it to MASM32:
http://www.madwizard.org/snippets/viewSnippet.php?s_ID=15

Sorry, I am lacking in this area. Let me see if I can hit the big points here. Actually, I'm using this version in my code:

__DEFAULT_FPU_SIZE__ EQU <REAL4>





;; examples:

;;    fmul fpc(10)

;;    fld fpc(<REAL8 -8>)

fpc MACRO val:REQ

	LOCAL w,x,y,z



	;; split type and value, defaulting to REAL4

	z INSTR 1,<&val>,<! > ;; TAB doesn't work!

	IF z EQ 0

		y TEXTEQU __DEFAULT_FPU_SIZE__

		x TEXTEQU <&val>

	ELSE

		;; REAL4 REAL8 or TBYTE

		y TEXTEQU @SubStr(<&val>,1,z-1)	;; Type

		x TEXTEQU @SubStr(<&val>,z+1,)	;; Value

	ENDIF



	;; should trim x of zeroes



	;; replace . with _

	z INSTR 1,x,<!.>

	IF z EQ 0

		w TEXTEQU x

		x CATSTR x,<.0> ;; prevent error message

	ELSE

		w CATSTR @SubStr(%x,1,z-1),<_>,@SubStr(%x,z+1,)

	ENDIF



	;; replace - with _

	z INSTR 1,w,<!->

	IF z NE 0

		w CATSTR @SubStr(%w,1,z-1),<_>,@SubStr(%w,z+1,)

	ENDIF



	;; figure out global name for constant

	z SIZESTR y ;; use last char for size distiction

	w CATSTR <__>,w,<r>,@SubStr(%y,z,1)



	IF (OPATTR(w)) EQ 0 ;; not defined

		CONST$fp SEGMENT

			w y x

		CONST$fp ENDS

	ENDIF

	EXITM w

ENDM

The addition is __DEFAULT_FPU_SIZE__ - which I use in other FPU macros for the default percision. If you don't specify a size for the constant then it defaults to the size defined by __DEFAULT_FPU_SIZE__. :P Here are some examples:

fld fpc(REAL4 2.5)

fmul fpc(REAL4 2.5)

fld fpc(REAL8 2.5)

fld fpc(REAL4 2.5)

fld fpc(10) ; no error for no period

The macro creates a global name for each constant that is created and attempts to reuse that constant if it is specified again. For example, above the constant value REAL4 2.5 is only created once, not each time it is used. All the values are defined in the segment named CONST$fp which keeps all the FPU constants together in the program, and also allows the programmer to do something like:

MyPI dd fpc(REAL10 3.14)

...which I guess isn't exactly useful, but basically means the macro doesn't interfere with the state of MASM and makes the macro very universal. :P

The macro assumes if your using the macro then you mean to create an FPU constant, so no trailing period and zero is required on values. What else do you want to know?

Doesn't really meet your requirements, but it offers IMO features which MASM itself should have internally, but doesn't. It would be convenient to programmer to use it. I have an MMX one, too.

Edit: When I write FPU values, it is usually to a structure or pointer that exists. So, I have no need to defined named writable values inline - as your macros allow. Same goes for MMX.

Hutch,
The FP Macros would be a welcome addition. Any chance of supporting all of the data types? I.E. Real, Int, Packed BCD.

The Packed BCD is great for converting Reals, and Int's to and from Ascii.