ObjAsm: boring notes

[HSE]

Are you sure?

Yes, what is expanded is a variable name, not a function. :t

[jj2007]

I would suggest that you test the snippet I posted above ;)

[HSE]

Yes JJ, I saw your snippet before to post.

Included in Demo03:

Code: [Select]

% .elseif [xbx].$Obj(XMenuItem).dType == MENU_TYPE_SEPARATOR
is expanded (in this case) to:

Code: [Select]

.elseif [ebx].OA_XMenuItem.dType == MENU_TYPE_SEPARATOR
and resulting code is:

Code: [Select]

CPU Disasm
Address   Hex dump          Command
004033CE  |> \837B 18 05    |CMP DWORD PTR DS:[EBX+18],5
004033D2  |. /0F85 82000000 |JNE 0040345A  ; almost forget this


[jj2007]

I see. So in

Code: [Select]

Only problem I see using AsmC are 2 or 3 ".elseif macro something" that I changed to ".elseif OA_something" the OA_something is not a macro but just an equate. That is indeed different from macro expansion :t

[HSE]

    If say macro, it's a macro:

Code: [Select]

: ————————————————————————————————————————————————
; Macro:      $Obj
; Purpose:    Return the mangled object name.
; Arguments:  Arg1: Object Expression: [Namespace:]ObjectName.

$Obj macro ObjExpr:req
  PreParseExpr ObjExpr
  if $ParseObjExpr(ObjExpr) eq FALSE
    .err <$Obj - syntax error: ObjExpr>
    exitm <>
  else
    %exitm <??ObjExpr>
  endif
endm
and if say textequ or equ .. mmmh