proc LikeThis uses esi edi eflags mm0, param1:dword, param2:dword
endp
    

macro prologuedef procname,flag,parmbytes,localbytes,reglist
 { local loc
   loc = (localbytes+3) and (not 3)
   parmbase@proc equ ebp+8
   localbase@proc equ ebp-loc
   if parmbytes | localbytes
    push ebp
    mov ebp,esp
    if localbytes
     sub esp,loc
    end if
   end if
   irps reg, reglist \{ 
    if reg eq eflags
      pushfd
    else
      push reg
    end if \} }    

macro epiloguedef procname,flag,parmbytes,localbytes,reglist
 { irps reg, reglist \{ reverse 
  if reg eq eflags
    popfd
    else
    pop reg
    end if \}
   if parmbytes | localbytes
    leave
   end if
   if flag and 10000b
    retn
   else
    retn parmbytes
   end if }    

irp mnem, push,pop {
  macro mnem val \{
    if val eq flags
      mnem#f
    else
      mnem val
    end if
  \}
}    

Extended syntax like push eax ecx edx ebx is just one irps away.

You're right, even FASM itself blunders on that (plain push 2 -1 compiles as push 1 despite explicit space; thank you, preprocessor).

revolution,

I forgot to insert smiley. Anyway, evaluator's greediness has nothing to do with this — look at preprocessed source.

I don't expect space to be an operand separator, FASM does.

push(1)(2)(3)    

I meant that evaluator has no means to detect that space was there: 2 -1 is indistinguishable from 2-1 after preprocessing.

And space is essential part of push/pop specification in manual.