why such syntax?

here new macro.like C

.outport (3f8h,byte 20h)
.outport (3f8h,word 20h)
.inport (byte 3f8h)
.inport (word 3f8h)

macro .outport port,val
{
done equ 0
match (parse@port,port
\{
match =byte parse@val),val
\\{

mov al,parse@val
mov dx,parse@port
out dx,al
done equ 1
\\}
\}

match (parse@port,port
\{
match =word parse@val),val
\\{

mov ax,parse@val
mov dx,parse@port
out dx,ax
done equ 1
\\}
\}

match =0,done
\{display 'OutPort ERROR...'\}
}


macro .inport port
{
done equ 0
match (parse@port),port
\{
match =byte parse@@port,parse@port
\\{

mov dx,parse@@port
in al,dx
done equ 1
\\}
\}

match (parse@port),port
\{
match =word parse@@port,parse@port
\\{

mov dx,parse@@port
in ax,dx
done equ 1
\\}
\}


match =0,done
\{display 'InPort ERROR...'\}
}


ı hope usefull for u.

dark_teo: starting macro name with "." in FASM, isn't a good idea

vid: or maybe, each label must start with "_"?
for example label:
._end or .__end


dark_teo: done equ 1 is not a good solution.
more memory needed to compile.
(fasm saves each value of "done" in memory, for restore command.)

label "._end" doesn't start with "_"

label names starting with "." have special meaning in FASM. In theory, this doesn't interfere with preprocessing, but in practise, people often use names like ".data" and ".end". These are awaited NOT to be overdefined by macro.