IncIncluder_Parser .
To enable it, you have to write:
PREPARSE IncIncluder
See Pre_Parser_concept, for PREPARSE rigid syntax. In most other Assemblers, when modifying a .inc Source File, that is ''include''ed in several Applications Sources, you may update all of these Applications at once. The ''IncIncluder'' Pre-Parser's purpose is to provide such an implementation by modifying a TITLE in as many Applications, that may make use of it.
Syntax:
PREPARSE incIncluder
INCINCLUDE D:\Path\Title.inc
Your Source must, of course, also have a:
TITLE Title
... reflecting the ''Title.inc'' File.
Each time you will re-compile your Source, if the ''Title.inc'' File has been modified, the Pre-Parser will substitute the modified File to your actual Title Part.
The File Max Size is 1 Mb.
All Statements are Case Sensitive: 'INCINCLUDE' must be upper case and the File Name cases must fit with the TITLE Name Cases.
When saving a TITLE Part with [Ctrl]/[S], if the actual Part is the one targeted by an INCINCLUDE Statement, you will be proposed to either save to the original Name.inc, or to save, in the usual way, the Name.asm into the current Directory. This allows you to eventually directly modify an .inc File from any PE making use of it, after modification in the Source Editor.
This implementation, while offering the main advantage of a classical inc Method, fully preserves all of the so important advantages of Mono-File Programming. Notice that, as opposed to the classical inc Method, this implementation is not recursive. This is to say, that an inc File can only be a TITLE part, and cannot include other sub-inc Files.
In order to save you from the usual management problems coming with external Files, you should provide the full Path and Name for your .inc File, in your INCINCLUDE Statement. Example:
PREPARSE incIncluder
INCINCLUDE D:\Programming\RosAsm\Includes\Macros.inc
And not use the default Directory with a lazy and dangerous:
INCINCLUDE Macros.inc
Doing it this way will, also, much reduce the conflicts possibilities, if you distribute your Application Open Sources, as others could, as well, also have a different Macros.inc File in their default Directory, for example... In case of conflict, your Application could not be recompiled on the other Computer - it would be modified -, whereas, when not finding the required .inc File, the Parser simply does nothing at all, this is to say that the Application is directly re-compiled from the actual Source as it comes.
When distributing an Application making use of this feature, you do not need to include the inc File(s), as it already is in the actual Source.
~~~~~~~