Jul.06.208 -- CAlive to introduce #reinclude pragma

[Rick C. Hodgin]

CAlive will alter the way #include files operate.  To prevent the need for having things defined in a particular order, #include files can be included in any order, and each of their features will be exposed to all programs, whether it was #included'd before or after the reference.  This will allow each #include file to be included one time, even if it is referenced in multiple places.

To accommodate the legacy needs of existing software, CAlive will introduce a new #reinclude keyword, which allows the specified file to be #included'd multiple times as needed, allowing a common file to be introduced as source code without replication.

By changing the definition of #include and introducing #reinclude, it is the hope of the CAlive authors (me, Rick C. Hodgin), that future software projects will be greatly simplified for developers, allowing required resources to be included one time and used throughout, rather than having to be done in a particular order.  And where a particular order is required, using #reinclude will allow that.

Note:  #reinclude has a double-meaning, it is to re-#include the file (meaning #include it more than once), but also it's a reduced include ability, in that by requiring files to be setup in a specific order, it reduces the utility of the #include feature, placing an undo burden on the developer.

-- 

Rick C. Hodgin