+2  A: 

One way to include assembly code is to add a wrapper function and write the assembly code in the asm block, as shown in the example below:

void wrapper_function()
{
    asm
    {
     /* your assembly code */
    }
}
xsl
A: 

You can also link in the object files. But inline assembler is much easier to maintain.

Gamecat
+1  A: 

You can use your makefile to define actions for different target types. For C types (e.g. foo.c) have the C compiler invoked. For ASM files, invoke the assembler. The output from either should be an object file (e.g. .o) which can all be compiled together by the linker.

If you have a little bit of assembly, go ahead an inline. Otherwise, I recommend separate modules and functional decomposition as the best way to manage everything. Especially if you need to support different targets (i.e. cross platform development).

Ray
A: 

Nice! And what about including exernal assembler functon code into Turbo-C program?

Ivan The Bear