I build a macro that let me know who operand its pass to a macro (example: it is a register, 1 byte, high; it is a segment, index; etc)
My intentions it use this macro to build new macros, I have a mov macro thats allow almost any movement from any operand to another operand (example: mov es,cs, mov [a],[b], etc) this macro, depending from the parameters generate the equivalent code (push cs, pop es, push ax, mov al,[b], mov [a],al, pop ax)
The first macro is tested and work fine, but for some reason when I call from another macro it works wrong or the logic operations works wrongs.

Lather I post all code.

rydemstorm,

Don't be so shy, post some (even still not working as you expect) code, maybe we can suggest something useful.

As a side note, higher-level constructions (or abstractions?) introduce another option for sub-optimal code, and (seemingly) we do have enough already.

I am work with MASM, TASM, NASM and FASM. Actualy I am teaching ASM using FASM, so I can not use the HL for my classes.
My intentions are to make macros useful but not as high as those used in HL.