I'd like to know how to use multiple .asm files in my assembly
projects.. now that i have RadASm this is much more possible
and convenient, and I'd really like to have more modular code.

My guess is it goes something like this:

Second asm file doesnt have "start:" or "end start", instead it
just has procedures.

First asm file has to somehow use those procedures..
perhaps it just has to have a function prototype for that
procedure, and RadASM will do the rest via linking all the
files together.

Anyways, I've tried something similar once before with little
success, and i've settled on using a main procedure in my
code, and calling it from the main loop.. just keeping every
thing tidy looking.
Posted on 2002-01-06 19:51:50 by matthew
I personally just use the 'include' keyword. I have one main asm file, then I put my protos in a separate file, my data in a separate file, etc. Then you just have to make sure that you put the includes in the right place. All i have to do then is compile the main file. This method works really well in an IDE like RadAsm or VC.
Posted on 2002-01-06 20:50:26 by sluggy
I prefer to divide my work (when possible) into smaller files by function. Usually, I use .inc files for definitions such as macros, structures, etc, things that do NOT generate .data or .code.

For those things like procedures and defined data, I start from an .asm and build it into a library. This library is added in with the includelib statement.

This may shorten build time, by leaving pre-compiled chunks of working debuged code unchanged.

Check out the MASM32 lib for hints on how to build a library. It's not well documented anywhere I know of, but its not hard at all.
Posted on 2002-01-07 00:05:02 by Ernie