Note that "namespace" by itself does not create a namespace.

PE::
namespace PE    

;@REM use windows CMD processor to build 
;@..\fasmg\fasmg.exe -e 5 %~nx0 %~n0.exe
;@PAUSE
;@GOTO:EOF

A::
macro _ X,Y,Z
  namespace A.X
    R='O'
    namespace A.X.Y
      Q='k'
    end namespace
  end namespace
end macro


_ B,C,?

display A.B.R
display A.B.C.Q    

Yet, how can "ExitProcess" be defined outside of the namespaces? (Something I'd like to avoid - should only be PE.Kernel32.ExitProcess.)

I have changed the version number to 0.99 with an update to interface that finally displays the content of line that caused an error. I try it with an algorithm that displays the line that came directly from source file and then, if an error happened inside a macro, also the final line at the deepest level that triggered an error. From my experience I think that this should provide needed information in most cases while not cluttering the error report too much.

When an error is triggered by ERR, that line is not shown. So when it is a macro that signals some error with ERR directive, the user is going to see the line that called the macro and the error message chosen by macro.

In addition I could also display the preprocessed text of that final line, maybe as a switchable option, but I have decided to not do it at the moment, because this feature would have some peculiarities (in fasmg preprocessing is limited to expanding the parameters and not the symbolic variables) and I need some more time to decide whether is it worth exposing.

Can the error, also report the Column Number ?

Do lines wrapped with \ are treated as one line of source or multiple?

jmg wrote:

Can the error, also report the Column Number ?

fasmg, just like fasm, operates on the pre-tokenized source that is far removed from the column numbers of the original text. Tracking the column numbers for every token would be very costly. I always thought that column numbers are not essential for a language like assembly which has one statement per line.

It might one one statement per line, but that expression can have a great many terms, commas and braces, especially within macros.

As the Column number is only needed when an error occurs, what about a system that re-token-counts just the error line, and reports a Char posn based on Token # ?

That has no speed cost to the main assembly process.

...This is under the assumption that we have at least a token number, but this may not always be the case...

The updated fasmg 0.99 shows the pre-processed content of line that caused an error.

;0.99

Might be faster if the listing can open and report directly to a file, with a reasonable size file buffer ?

Another question:
I see manual.txt mention of proc/endp macros, which look like they can manage unused/dead code removal, via the multi-pass feature, but that is not explicitly stated ?

Can something as universally useful as dead code removal structures, be included without needing slower macro includes ?

jmg wrote:

Might be faster if the listing can open and report directly to a file, with a reasonable size file buffer ?

The main reason why listing macros add so much time to the assembly is that every single line gets expanded into this long macro (since "macro ?" intercepts almost all the source lines). The othet option could be to make this macro as short as possible, only collecting the values that could then be processed into a listing text in the postponed block. Also, if the redirected display is not buffered properly in your environment, then in the postponed listing the entire text may be generated into a VIRTUAL block and then displayed as a single block. I may try such a variant later, when I get some free time.

000000B1: 05 14 E8 6D             qIF_Z qXOR 0AH,#05H WC
000000B5: 05 14 E8 6E             qIF_Z qXOR 0AH,#05H WZ
000000B9: 05 14 E8 6F             qIF_Z qXOR 0AH,#05H WZ,WC
000000BD: 05 14 E8 6F             qIF_Z qXOR 0AH,#05H WC, WZ
000000C1: 05 14 68 6C             qIF_Z qXOR 0AH,#05H NR
000000C5: 05 14 FC 6C             qXOR 0AH,#05H
000000C9: 05 14 FC 6D             qXOR 0AH,#05H WC
000000CD: 05 14 FC 6C             qIF_ALWAYS qXOR 0AH,#05H
000000D1: 05 14 FC 6E             qIF_ALWAYS qXOR 0AH,#05H WZ
000000D5: 05 14 FC 6F             qIF_ALWAYS qXOR 0AH,#05H WZ, WC
000000D9: 05 14 7C 6F             qIF_ALWAYS qXOR 0AH,#05H WZ, WC, NR
    

if used external
        external = 0
end if

namespace proc
        use = external
end namespace    

omasz, how hard would it be to convert
https://github.com/tthsqe12/asm/tree/master/asmFish
into the new fasmg and possibly get a version for the mac os?