Yes.
#include "string.dba"
or whatever.
I also like it for adding "new code".
There are some "gatcha's" though ...
1 - If using Dark Edit's preprocessor commands,
you will need to "replace source". This can cause problems.
So, first save your file, Then, save your file with an extra tag
example:
"stringDE.dba" - this would be Dark Edit Source code
"stringdba.dba" - the would be the "replaced Source"
The replaced source would then be ready to use as an include file.
2 - Since the code gets changed to make an include,
you will need to provide alot of documentation in your includes
as to how to use everything.
3 - Of course, you can simplify things just by not using the
preprossesor directives. After all,
Global AVar
just gets changed to
Dim AVar(1)
and
Type SomeType
Var1
Var2
EndType
Just goes to
Dim SomeType_Var1(1,50)
and so on
The Defines are nice, but don't always work either.
The way I manage "new code" is to place bookmarks (actually a line marker just like using a goto or gosub) at key points, and try to key new code in a function of its own. This helps with debugging.
We all know the bebugger gives errors from time to time, so,
work in a small area. Before moving to another area in code, try compiling. If it crashes, check your last changes. There is nothing more frustrating that making many small changes throughout your program, go to compile and have it crash to the desktop without no clue as to where to begin looking

Keep changes localized.