; sets the format of the file and also set the model flags for use with _declaresegment
; the main difference between format and .model is that a comma separates
; the format type from the flags when using .model
; i.e. .model pe
;       .model pe, gui <-- comma separates format flag from type
;       .model coff
;       .model ms coff ; <-- does not need a comma between ms and coff
macro .model name, [args]
{
   common ModelFlag$$ = 0

   match =pe, name
   \{
      ModelFlag$$ = 1b
   \}
   match =ms coff, name
   \{
      ModelFlag$$ = 1b
   \}
   match =coff, name
   \{
      ModelFlag$$ = 10b
   \}

   format name args
   _segment ModelDummySegment$$
}

; use the macro .segment to declare a new segment (or one previously declared)
; dont use this one directly
macro _segment name
{
   local mac
   __#name equ __#name, mac
   macro mac
   {
}

; internal macro to *really* declare the segments, do not use directly
macro _declaresegment name
{
   common

   if ModelFlag$$ and 1b
      match =text, name
      \{
         section '.text' code readable executable
      \}
      match =data, name
      \{
         section '.data' data readable writable
      \}
      match =bss, name
      \{
         section '.bss' readable writable
      \}

   else if ModelFlag$$ and 10b
      match =text, name
      \{
         section '.text' code 
      \}
      match =data, name
      \{
         section '.data' data 
      \}
      match =bss, name
      \{
         section '.bss' data
      \}

   end if
}

; macro to declare and write all segments in order
; do not use this directly, use .end
macro _end [segments]
{
   common
   local mac
   macro mac dummy,[n]
   \{
     n
     purge n
   \}
   forward
   _declaresegment segments
   match I, __#segments
   \{
      mac I
   \}
}

; use these two instead of _segment and _end
.segment    fix } _segment
.endx        fix } _end ModelDummySegment$$ ,
    

include 'win32w.inc'
include 'segments.inc'

.model ms coff   ; same parameters as format (so dont use format directly)
public testproc

.segment text

proc testproc
local temp
      ; .... code
      mov   eax,[temp] ; <-- sup with the temporary label being temp?Pi ??
      ; .... code
endp

; resource.inc already defined .end.... the segments.inc file will have few new names to reduce pollution in namespace
.endx text   

    

; example of simplified Win32 programming using complex macro features

include 'win32wx.inc'
include 'segments.inc'

.model pe,gui 4.0

;-- START
.segment text

  start:
        invoke   MessageBox,HWND_DESKTOP,str1,str2,MB_OK
   invoke   ExitProcess,0

.segment data
str1 TCHAR "Hi! I'm the example program!",0
str2 TCHAR "Win32 Assembly",0

;-- STOP

.endx text, data
.end start
    

Am I right in understanding that when you include a file, its the same as if the included file was embedded *unmodified* in the source at the point that you included the file?

Mercury Knight wrote:

Am I right in understanding that when you include a file, its the same as if the included file was embedded *unmodified* in the source at the point that you included the file?

You can't break a macro between files. Your .segment macro is opened in the included file but not closed until .endx is encountered.